Gutenberg v10.1.0 - Crashing editor/browser when latest Instagram posts block is added

[khristiansnyder]

1. On both AT and simple sites with Gutenberg 10.1.0 active...
2. Add the Latest Instagram Posts block and connect it to an Instagram account and try to publish the page. (Or open a page where that block is already published)
3. The editor crashes and uses a tremendous amount of browser resources.

Browser / OS version

Chrome Version 88.0.4324.192 (Official Build) (x86_64)

Does this happen on simple or atomic sites or both?

Both

Is there any console output or error text?

Level of impact (Does it block purchases? Does it affect more than just one site?)

Affects any editor that has the Latest Instagram Posts block connected to an Instagram account.

Reproducibility (Consistent, Intermittent) Leave empty for consistent.

Screenshot / Video: If applicable, add screenshots to help explain your problem.

[jordesign]

I've been able to recreate on a WPCOM simple site as well.

Different console error though..

Uncaught TypeError: Cannot read property 'querySelectorAll' of null
    at setAriaExpanded 
    at HTMLDocument.init

[jordesign]

Also recreated on a Vanilla WordPress installation with TT1 active and only Jetpack and Gutenberg plugins installed.

[gwensmithx]

This seems to be related. I have a customer on a simple site and Instagram gallery block was crashing the homepage. I opened the Classic Editor and removed it.

#28053687-hc / #3794424-zd

[jordesign]

Another user affected in #28193265-hc. they're going to wait out the fix

[pablinos]

Noting that Gutenberg 10.1.1 has been released (p7DVsv-aMy-p2) to WordPress.com, which solves this issue.

[Gilmoursa]

Unable to reproduce in Gutenberg 10.1.1. Closing the issue