-
Notifications
You must be signed in to change notification settings - Fork 18
Severe performance regression on IntelliJ 2026.1 / Windows 11 — language_server_windows_x64 high CPU usage, freezes, very slow refactoring #306
Description
Title: Severe performance regression on IntelliJ 2026.1 / Windows 11 — language_server_windows_x64 high CPU usage, freezes, very slow refactoring
Summary
I would like to report a major malfunction that I have been experiencing for several days with the JetBrains plugin.
The process language_server_windows_x64 is now consuming an excessive amount of system resources, reaching more than 80% of total system usage. This behavior did not occur before.
As a result, the IDE becomes extremely slow and can sometimes freeze completely.
In parallel, processing times have become abnormally long. Even a simple refactoring operation can take between 30 minutes and 1 hour, which makes the tool very difficult to use on a daily basis.
I am also noticing what appears to be disproportionate token/credit usage, while the overall quality of service has significantly degraded.
Environment
- IDE: IntelliJ IDEA
- Build:
IU-261.22158.277 - Build date: March 25, 2026
- OS: Windows 11 Pro 22H2
- OS build:
22621.4317 - Windows Feature Experience Pack:
1000.22700.1041.0 - CPU: Intel(R) Core(TM) i5-5300U CPU @ 2.30 GHz
- RAM: 16 GB
- Architecture: 64-bit OS, x64-based processor
Observed behavior
language_server_windows_x64uses an excessive amount of CPU/resources- severe IDE slowdowns
- occasional full system freezes
- refactoring tasks can take 30 to 60 minutes
- token/credit consumption seems abnormally high compared to the work actually completed
Expected behavior
- normal CPU/resource usage
- responsive editing and refactoring
- no system freezes
- processing times consistent with previous versions / normal usage
- token/credit consumption proportional to actual work performed
Impact
This issue makes the plugin extremely difficult to use in a professional daily workflow.
Request
Please investigate this regression and identify the root cause as soon as possible.
If needed, I can also provide additional logs, stack traces, or reproduction details.
Not found: an internal error occurred (error ID: b5de0d4b6eaa4530912e877ebc4dada8) (trace ID: c31b2dfe15e380c73ac2ab4932867a70)