Blank post edit screen after updating to 4.0.0 (conflict with JavaScript Errors Notifier chrome extension)

[ekapobc]

Describe the bug
I have created a Gutenberg post with a previous version that includes most of the blocks for testing purpose. After updating to 4.0.0, the edit screen went blank with some JavaScript errors in the console. I have already tried switching to the default Twenty Seventeen theme, but no luck.

To Reproduce
I am not sure about the exact steps to reproduce it. Basically, the Gutenberg post that currently has the problem includes most of the blocks created with Gutenberg version prior to 4.0.0.

Expected behavior
The post edit screen should work fine.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Chrome
• Version 69.0.3497.100

[designsimply]

Thank you for testing and for posting a screenshot!

Here are the errors that look relevant to me:

TypeError: Converting circular structure to JSON
Uncaught (in promise) TypeError: Converting circular structure to JSON

I have seen those errors once before in #10490 and they found that it was caused by a conflict with the "JavaScript Errors Notifier" chrome extension ( see #10490 (comment) ). If you have that extension, or any similar one, could you try disabling it temporarily to see if it makes the problem go away?

[ekapobc]

Yes, disabling the extension resolved the issue. Thank you!
So, I am curious whether it would be the job of the Gutenberg team or the extension developer to fix this incompatibility in the future version?

[designsimply]

Each case is unique and I think the answer depends a bit on exactly where and how the conflict is introduced and I don't know the extension well enough. That said, notifying the extension developer of a conflict a step that can't hurt.

Aside: I just tested installing the JavaScript Errors Notifier extension with Chrome 70.0.3538.110 on macOS 10.13.6 and then opened the Gutenberg demo post and did not see any errors in the console so either something has been resolved in the mean time (or maybe the issue is specific to Windows?). I tested with WordPress 4.9.8 and Gutenberg 4.5.1.