CLion on Mac is a CPU hog
Has anybody noticed that? It seems to be very busy "parsing syntax" all the time, but even when minimized, Activity Monitor shows it takes between 92% and 200% of my CPU! that's with the latest 1.2 EAP, but even 1.1 has that behavior... On laptops, it's really bad, the battery goes very quickly. I barely have any plugins installed. Is there anything else I can do to get the CPU consumption back into normal range?
Thanks!
Frank
Please sign in to leave a comment.
Hi, Michel,
We are working hard on CLion performance improvements, but it seems that some important fixes will be ready only for CLion 2019.1.
If you would like to investigate the performance problem you've faced, please send a CPU snapshot to clion-support at jetbrains.com.
Could someone please translate this post into something readable?
As I read it, the OP is having high load issues when syntax highlighting enabled. The OP then claims it was fixed by a reboot? I don't think we are discussing the same issue.
Sorry, my english is terrible.
Yes, I had a problem with incredible CPU load during highlighting and syntax checking right after installing CLion.
And it disappeared strictly after a reboot.
In the "Activity monitor" built into the CLion, the main process that hung out my system was exactly (cidr.lang.symbols).
And it is quite possible, because many poppy users reboot it about once every couple of months with the arrival of updates.
Since the problem disappeared, I did not have time to make a CPU snapshot that would show this situation in more detail.
I really didn't think it would work.
Thank you for that clarification.
The new version of CLion (2019.1) seems to be yet another step backwards. As I type this, CLion - which is open in another desktop window doing nothing of note - is causing 580% CPU usage on my laptop. People in my office are starting to stare at me, presumably because of the torrent of noise coming from my laptop fans due to CLion's obscene CPU usage.
@Dcooke, please capture a CPU snapshot using CLion 2019.1 and send it to clion-support at jetbrains.com so that we could investigate the situation.
@Anna Falevskaya Sent. I must say that if performance isn't substantially improved very soon then I'll be saying goodbye to CLion. This has been a problem for years now and it rarely seems to get better with new releases, often worse. There's no point in keeping asking for CPU snapshots if addressing the problem isn't a priority, and based on your previous promise - "We are working hard on CLion performance improvements, but it seems that some important fixes will be ready only for CLion 2019.1." - I don't believe that it is a priority at all.
@Dcooke, I’m sorry you feel that way about the product. Performance and stability are indeed our priorities and we keep constant work in that direction, improving this step by step. By important fixes in 2019.1 I meant reworking code highlighting and quick-fixes. And we did that: now Clangd is used for them which means editor performance improvements (and some of our users have noticed that). We plan to continue moving more of the IDE’s actions to Clangd-based engine. There are still many performance problems for certain. But we keep working on them, this work just takes time.
Using clion 2019.2 on a 16G 2.2 GHz Intel Core i7 macbook pro, same issue. Nothing works
I'm having now a problem with the memory usage of CLion. The CPU usage has gone back up since my last positive comment, but now it's the memory usage that is taking over 8GB and then asks to get more....
Dear all!
In CLion 2019.3 we plan to work intensively on various performance boosts, including some massive overhauls we started earlier this year. Please see our roadmap for more details. If you're interested in our situation with performance, please follow updates in our blog. You can expect a series of blog posts covering the progress and explaining the underlying ideas, with some measurements on referenced projects so that you can compare them with your cases.
As for the particular problems you're facing:
Unfortunately, we can't do anything without actual CPU snapshots and thread dumps. There are dozens of different environments and setups, we can’t estimate or directly help with your particular issues, unless you share some additional info with us.
So if you would like to investigate the problems you've faced, please send to clion-support at jetbrains.com a CPU snapshot if you manage to capture it or, in case of complete freeze, some automatically generated thread dumps which are located in the logs folder.
Clion makes my mac fucking hot
Are there any further updates regarding performance improvements? It seems 2019.3 changed little. The single biggest problem with CLion is that it consistently has 400+% CPU usage whilst I'm doing literally nothing with it - not even browsing code. What the heck does it need this CPU time for!?
I've waited for a long time and moved to vscode - it has real remote development - so the indexing is all on a powerful Linux machine so my Mac is no longer bogged down.
@... Just started trying vscode... all of the features I need with < 1% CPU usage. Goodbye CLion.
I also just moved to VS Code and uninstalled CLion. In the beginning, VS Code needs a bit of effort to learn how to set-up a project, but it's worth it.
Update:
We keep working on performance improvements in CLion. New 2020.1 EAP is now opened with Data Flow Analysis (the heaviest analysis of all) is now moved to Clang and hopefully work faster: https://blog.jetbrains.com/clion/2020/01/clion-starts-2020-1-eap/#dfa
Next step for us will be implementing some lightweight PSI inside CLion to substitute the fully correct tree used for many smart actions where possible. This is a huge architectural change we've already started the work on. I do hope we'll be able to show some results soon, maybe even in 2020.1. Stay tuned.
I am using CLion 2020.1 on MacOS Catalina 10.15.5
It's draining my battery at a very fast rate.
I'm using both vanilla settings on my mac and on Clion, nothing modified.
This is bothersome, the battery drain is unreal. 30% battery drain in just within an hour.
Please fix this.
It is a problem for me and my team to work.
It's not a common problem happening to every mac user and thus requires an investigation, so please submit CPU snapshots to our support or issue tracker so that we can help you.
Sorry for resurrecting this old thread, but I just found it and am experience a similiar battery draining situation on my MacBook Air M1 using CLion 2023.2 with the new UI.
Anastasia Kazakova I tried to create a CPU usage profile, but it just crashed on me during a build! I will try to invest some more effort.
Sven Schober Please report an issue to the issue tracker with IDE log and, if possible, CPU profile. We haven't seen it for a long while, maybe it's smth new
It seems, there is already an issue (see [1]) with a similar observation - would it be ok, if I just chime in there?
[1]: https://youtrack.jetbrains.com/issue/CPP-34132/Huge-CPU-usage-on-CLion-on-macOS
Sven Schober Yes, please attach your snapshot there. And then also please try out this workaround: https://youtrack.jetbrains.com/issue/CPP-34132/Huge-CPU-usage-on-CLion-on-macOS#focus=Comments-27-7961746.0-0. Let us know if it helps in the ticket comments. Thank you.