[nybblesio]

You may want to give the CLion 2019.3 EAP build a try. I was having the same issues as you with a very large (~1 million SLOC) C++ code base. To my surprise, the EAP build has seemingly removed almost all hesitation/hanging. They did rename the keymaps for some odd reason, which I worked around by extracting from a previous version's resources.jar file and placing in my preferences directory.

[cmrdporcupine]

I have been using it. No real improvement. Freezes all over. And I gave the GC something like 20gb.

It's even worse when adding in our internal repositories on top.

Also having a back and forth on a ticket about their support for compiler_commands.json; the one generated by ninja for Chromium simply doesn't work for me. Their person says it works for them, though. I don't know how. Right now I manually create a CMakeLists.txt with the directories I need.

But one thing that is discouraging about CLion is that even directories that you explicitly tell it not to index as source seem to still be looked at and indexed in some fashion, so a huge number of files just drags it down to a halt. My coworker was able to get decent performance by creating an empty directory and symlinking in only the directories he is working on. Simply having directories with large quantities of files is enough to drag it down.

It's very disappointing, as its my tool of choice. I feel handicapped without it.

[derpscot]

20GB what? Xmx? That high is going to cause you really massive GC pauses... Maybe try winding that down a bit?

[cmrdporcupine]

I've tried everything inbetween, so.