@zoonini I’m talking about the production version of Gutenberg. It DOES have some freezing but not as bad as the plugin.
@moviedebuts Thank you for the clarification, it’s helpful.
But let me just say that I’m a content person, not a programmer. I wouldn’t know how to interpret the various tests you suggested.
That’s OK – you don’t need to interpret any of the troubleshooting steps I mentioned!
Is anyone from Gutenberg working on this problem?
I’ve done some searching in the Gutenberg bug repository over in GitHub, but I couldn’t yet find any existing reports that quite match the freezing/slowness described here, nor have I been able to replicate it yet on a test site, which is why I’ve been asking the folks who chimed in here in this forum thread for as much information as possible about when the issue occurs. I also spoke to one of the Gutenberg issue “triagers” (someone who’s very familiar with all the current bugs and issues) and this did not ring any bells for them.
https://github.com/WordPress/gutenberg/issues
I’m still interested in what you said here, as it’s a big clue:
after installing the health plugin and having the troubleshoot function on, the editor is so amazingly fast, i cannot remember ever had such a fast wp-editor.
When you’re in troubleshooting mode, all your plugins are temporarily deactivated. If the block editor is speedy in troubleshooting mode and doesn’t freeze up or lag, that’s a good sign. It means that one (or possibly more) of your plugins might be somehow interfering with the editor, causing the freezing. The trick is to figure out which plugin that might be.
In troubleshooting mode, you can try reactivating your plugins one at a time. After reactivating each plugin, test the editor again, and see if it lags/freezes. If it’s speedy and zippy but suddenly bogs down again when you reactivate a certain plugin, then it may be that this specific plugin has an issue with the editor in WP 6.0. I’d be interested to hear the results of this kind of testing, when/if you’re able. Thanks!