clangd 100% CPU usage on 2020.2
Completed
2020.2 is completely useless, not only is cland going to 100 percent cpu usage on an 8 core I9 but it also hangs so even when CLION is closed there is a running clang process eating CPU.
Please sign in to leave a comment.
Hi Richard!
Sorry for the inconvenience. Please do Help | Collect Logs and Diagnostic Data and send the resulting archive to clion-support at jetbrains.com. Note that logs might contain private user's information (like file paths and names).
Also please capture a CPU snapshot while reproducing the issue and send it to us.
I see this, too. It's not new in 2020.2. It's quite common. Just saw it in 2020.3.
Richard Swanson in CLion 2020.2 we had a regression - https://youtrack.jetbrains.com/issue/CPP-21654. Maybe you were affected by it. But still we need diagnostic information from you in order to determine the exact cause instead of guessing.
Steve Lautenschlager if you would like to investigate the problem you're facing, please collect the diagnostic information I requested in the previous comment and send it to clion-support at jetbrains.com.
Anna Falevskaya I went back to 2020.2 and have not been able to reproduce the problem.
I had the same problem, CPU 100% for the clangd process (CLion 2020.2). Invalidated caches and restarted, now clangd just crashes, and disables clang-tidy. Given up for today, I'll try create a minimal project tomorrow.
@... please send an email to clion-support at jetbrains.com and we will try to help you.
I'm using CLion 2020.2 on FreeBSD, and there is no official support for FreeBSD... can I still send in a support request?
I can't reproduce the 100% CPU anymore, since invalidating cache and restart.
I can reproduce the crash though..., (also self-resolved https://youtrack.jetbrains.com/issue/CPP-18725#focus=Comments-27-4355571.0-0)
@... thanks for sharing the details in the YouTrack ticket, that's enough I think, no need to submit another request.
It's getting worse and worse with every single version since clangd integration. I use Clion from version 2019.2 with remote development support. Now it works only for "hello world" projects. While opening a bigger project with large cc files, the analysis is running over and over while typing taking constantly one or two CPU forcing me to disable analysis completely.
Highlighting can be changed per the file from "All problem" to "Syntax" but only after switching to "None" Clion start to be responsive enough. I started refactoring and have a lot of problems (96 errors and 11 warnings on 800 lines of code) and Clion freezes for e.g copy-pasting?
I just feel that the integration clangd wasn't the right move. Sincerely, the only thing that keeps me is remote build and debug, which works pretty well in newer versions.
Might be not programing on a notebook where I can hear a fun cooling CPU I would not be so angry about it.
This issue is really annoyed. Make it impossible to continue working with CLion.
Yup, same here; CLion unusable for me again - back to VSCode, I guess ((
Hi all!
There is no one universal performance problem, all performance-related issues might be caused by different reasons in each particular case. Therefore we need additional information in order to investigate the particular issue you're facing:
Please do Help | Collect Logs and Diagnostic Data and send the resulting archive to clion-support at jetbrains.com. Note that logs might contain private user's information (like file paths and names).
Also please capture a CPU snapshot while reproducing the issue and send it to us.