Goland causing severe CPU thrashing after update to 2026.2 (on ubuntu linux)
Hello,
A few days ago, I upgraded the Goland from 2026.1.6 to 2026.2.2.1 and now when I launch goland, it tries to “Analyzing project” almost every time I open the IDE with the same project. And when its doing this, all 16 of my CPU cores goto near 99% usage(there is nothing else running and the system is freshly booted). I can't even do a Google meet call or screen share while its “Analyzing project”, as it just sucks up all the available resources.
Here's what I tried to remedy, to no avail:
1. enable GPU acceleration via Help→ Edit Custom VM options (have nVidia 4060 GPU)
2. switch back to X11 from wayland: “-Dawt.toolkit.name=XToolkit” in Help→ Edit Custom VM options
3. increased memory from 8GB to 16GB (even a single small project get “Analyzing project” with all 16 CPU cores hammered to 99%)
Mine is ubuntu Linux system on 24.04 LTS
Thank you. Logs uploaded: Upload id: 2026_09_15_iur6YqLJpYvY8ATyK4gJ45 (file: goland-logs-20260915-1754339429047260287201799.zip)
Please sign in to leave a comment.
Also, even after the “Analyzing project”, which takes unusually long time to complete, the IDE is still laggy.
intellisense when writing code lags so much that often auto-complete does not even function. I have to wait several seconds after writing to wait for intellisense to catch up (something never happened in 2026.1.*)
If I open a react project within Goland, and try to insert a dependency's import path (alt + enter), the initial options are almost always wrong (it seems some kind of local ai model runs and gives generic ai options). I have to press alt+enter sever times to get the correct options (ones that give the option to add import path). Its just annoying and very bad optics for the IDE especially when I am screen sharing and explaining code to my team members.
overall, I would like to ask if its possible to revert to 2026.1.6 from 2026.2.1 for me as that worked fine for me
It looks like two separate things are going on.
The IDE runs a full project scan on most launches, instead of reusing the index filter it saved on the previous run. Across your logs it skipped that scan 13 times and ran it 46 times. When the scan does run, indexing sizes itself to one less than your core count. That claims 15 of your 16 logical cores and leaves one core for everything else, which is why a call or a screen share cannot survive it. The longest single pass in your logs took just over 17 minutes.
What I cannot yet explain is the repeated scanning. Quitting without a clean shutdown does invalidate the saved filter, and that covers 19 of the 46 scans. The other 27 happened after a clean shutdown, so something else is resetting it too. I would rather track that down than guess.
For immediate relief, cap how many cores the IDE can use. Open **Help | Edit Custom VM Options** and add this line:
```
-XX:ActiveProcessorCount=8
```
That limits the whole IDE to 8 cores. Indexing then takes longer, but the other half of the machine stays usable. Use a lower number to leave more cores free during calls.
The test that would tell us the most:
1) Open a single project, and let "Analyzing project" run to completion without interrupting it or starting work in another window.
2) Quit GoLand through its own menu, not by closing the window and not by ending your desktop session.
3) Reopen the same project, and tell me whether it scans again.
Step 3 is the answer I need most. If it still scans, repeat the three steps with downloaded plugins switched off (**File | Settings | Plugins**, then the gear menu, **Disable all downloaded plugins**), and keep to one project window. Your logs show four project windows each starting a full scan inside four minutes, which multiplies the cost.
After that, please send fresh logs from **Help | Collect Logs and Diagnostic Data**. Upload the archive to https://uploads.jetbrains.com and post the Upload ID in this thread. The ID is safe to post publicly, only JetBrains can open the upload.
One more thing from your logs: your Go SDK moved from 1.26.0 to 1.26.5 during this period. Every SDK change re-indexes roughly 7,400 SDK files per project, and the prebuilt index GoLand ships covers 1.26.0 and 1.25.7 but not 1.26.5. I am still checking whether that gap is expected, and it is a separate matter from the repeated scans.
On rolling back, yes, that works. In Toolbox App, open the options menu next to GoLand and select **Available versions**, then install 2026.1.6. Toolbox can keep both versions installed, so you do not have to drop 2026.2 to compare them.