Performance and memory problems

Since CLion tries to parse your whole code base, including all the header files used, to understand your code correctly and provide accurate code completion, code navigation, refactorings and other intelligent features. On large code bases (especially when using Boost), performance and memory issues during indexing and editing are possible.

Increasing memory may help to resolve performance problems. To check the memory usage, enable the memory indicator in Preferences/Settings | Appearance & Behavior | Appearance | Show memory indicator.

To report a performance problem, please follow these instructions. To find IDE logs to attach to the problem, use this link.



Are there any other actionable items for performance issues? I have more than sufficient memory available sitting unused, yet something as simple as toggling between header and cpp file takes 10+ seconds. CLion performance seems to have steadily degraded over the past year I've been using it to the point that it's bordering on unusable for me now.


Any updates on this? I have the same exact issue with base IDEA.


I enabled the memory indicator as suggested, where would I expect to see the indicator?


It's in the bottom right corner of the window


Do we have any solution for this performance issue? I am using Pycharm inside my virtual box and its eating all my memory and slows down my performance. How can I fix this performance issue. Please suggest.


Having very similar issue with IDEA.

os: macOS mojave

cpu: 8th gen i7

mem: 16gb @ 2400mhz

Intellij IDEA @ 2018.3.1

No matter how much memory I've allocated to IDEA, it tries to consume it all and the editor gets really slow and non-responsive. I've allotted 1 -> 1.5 -> 2 -> 2.5 gb of ram and it still eats it all up. Doesn't matter what its set to.

This is a serious issue and extremely bothersome. May be going back to vscode if this doesn't get resolved.


I am having the same problem.  I set the heap to 2g so that I can get more time before the memory is used up.  

I may not continue my subscription and just switch to vscode.   This problem has been around for a long time and has never been resolved. 

FYI - I get this with a clean setup developing angular projects. 


2Gb is a default xmx value. I would recommend you to increase the value for Angular project. Also you can provide the memory snapshots to our support for further investigation, especially if you suspect some memory leak.

I run Node, Angular dev server, MongoDB and Apache Livy outside of IntelliJ Ultimate in Iterm sessions.   
The only thing running in Intellij is the editor and sometimes the debugger.   The memory shows around 250mb when I first start and after about an hour or 2 it increases close to the 2G max that I have set.   This has been happening for about a year and I have tried every version of Intellij with the same problem.
Is this a bug with the typescript support ?   -  When I switch to my Scala / Spark projects I don’t have this problem. 
Not sure how to take a memory snapshot but will search on how to. - John

My CLion (2018.3.4) goes crazy with memory usage. It starts normal but sometimes at reloading my CMake it hangs some minutes and than shows the "Out of Memory" window. I already allowed -Xmx 20'000 MB but it still happens. This cannot be normal right?




I've just upgraded phpstorm from 2018.2.1 to 2019.1 and memory issues started immediately. increased Xmx to 2GB, Activity monitor shows 2.53GB in use, and still feels slowish at times. 



Same with Intellij (no surprise) - I have Xmx to 7750m and using IDE for ~4 hours ends with about 4.5 GB unreleasable memory....


to be fair the problem was gone next day, can't attribute that to anything. I disabled few plugins when I was having the problem and even was in running in PowerSave mode, but nothing make any difference. Next day I began work expecting to be annoyed by the memory issue, but quickly forgot about that until I realized it was gone, I'm hitting 700MB average, just like before. go figure ¯\_(ツ)_/¯ 


Edited by Gsegura

Please sign in to leave a comment.

Have more questions?

Submit a request