High CPU usage with Chrome and CKEditor 4

Hi everyone,
we are using the paid version of LanguageTool and are quite happy with it! It always worked perfectly. However, something has been changed, and our editors cannot use the LanguageTool extension anymore with our CMS. The problem is high CPU usage that causes huge lags. When the extension is disabled, the problem is solved.

We have experienced this issue on Windows and MacBook Air M2 16GB, both OS with Chrome Browser.
LanguageTool Version: 8.17.0

Our CMS setup:
We have multiple instances (14 instances) of CKEditor 4.16.1 on a single page. The editors are initialized but hidden (like an accordion).
When every section is open, the performance gets better, but it’s still not usable.

We have tried to set CKEditor instances as “readOnly” if it’s in a hidden state. That solved the issue of a permanent creation/deletion of the LanguageTool toolbar that was visible in DevTools. However, the lag remained the same.

We also tried using spellcheck="false" on the textarea, but that didn’t help either.

We can share a staging environment with you for testing.

Looking forward to your support! Thanks in advance.

Best regards,
Daniil
inside-digital | nextpit

1 Like

Hi, thank you so much for reaching out. We are currently unable to replicate this issue. Can you provide us access to the staging environment? You can reach me at christopher.blum [at] languagetool.com

I’m experiencing the exact same thing on Chrome. When I turn of the extension, the problem goes away. I have a Macbook Pro M4 Pro with 24GB of RAM.

For the moment I turned of the extension but would like to use it again.

We are still looking for a way to replicate this issue.
@dantio if possible, please share access to a staging environment with us. Many thanks in advance.

@tiff I have already sent the staging access to you. I hope you received the email and the login worked.

1 Like

We have released version 8.18.4 of our Chrome extension. You can enforce the update by reinstalling. Please let us know if the issue has been resolved. Thanks in advance.

@tiff Thank you very much. We can confirm that v8.18.4 fixed the high CPU usage. :tada: