-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High CPU usage when simply typing in paragraph block #7498
Comments
I just downgraded to 3.0.1 and no longer have this problem, so it definitely was the 3.1.0 version. With 3.0.1 the highest CPU usage a Gutenberg page uses while typing is ~50% typing as fast as I can. |
Yeah, I notice this too right now. Related #6466 |
Investigated the issue and found the change here: #7680 (comment) |
This is still a big issue in WP 5.3 making Gutenberg unusable (I have to use the "Disable Gutenberg" plugin in prod). I get the same result as below in https://frontenberg.tomjn.com/ FYI in the example post above, I have about 70-80 blocks (hidden above) with 90% text and titles 10% custom HTML blocks. NO Active Plugins. Using Chrome 78.0.3904.87 (Official Build) (64-bit) MacOS 10.13.6 Let me know if you need more diagnostics. |
There's a need for this to be viewed again. High CPU usage on a span of 6 processes created by Gutenberg. |
Describe the bug
Ever since the latest update to 3.1.0, typing in the Gutenberg editor thrashes my CPU. I've tested this on my local site and also using Frontenberg (just to see if it was my setup). Whenever I stop typing, CPU usage drops dramatically. I don't remember this being an issue with the previous version, but it at least wasn't as bad because I didn't notice. Right now I can't even type without serious lag.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect just typing to not use 100% of my CPU and lag so much that I can't see what I'm typing without buffering.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: