[linux] Clion freezes (even in small projects)

Answered

I use clion for competitive programming and sometimes it freezes. I want to fix this, but I don't know where the problem is. Help me please.

CLion 2018.3.4
Build #CL-183.5429.37, built on January 31, 2019
JRE: 1.8.0_152-release-1343-b26 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.20.7-arch1-1-ARCH

threadDump.txt

0
5 comments

Hello!

Performance problems may be caused by an insufficient amount of memory. Please try enabling memory indicator (File | Settings | Appearance & Behavior | Appearance | Show memory indicator) and keep an eye on it for some time (the indicator will appear in the bottom right corner of the CLion window). If it is close to the limit at the time when you are experiencing the problems, then try increasing the Xmx JVM option according to this guide

We're constantly working on performance issues. For example, in CLion 2019.1 EAP we started to use Clangd for code highlighting and quick-fixes which means editor performance improvements - https://blog.jetbrains.com/clion/2019/01/clion-2019-1-eap-clangd-mute-var-rename/. You can try using CLion 2019.1 EAP.

0
Avatar
Permanently deleted user

I found out that this happens when I open clion and when code starts to compile I open another window. I don't know why is this happening.

0

Anna

 

I have noticed constant freezes since the clangs introduction. I am going to downgrade to a 2018 version to double check, this is on template heavy code. A lot of my classes are mixin style implemented like this:

template <typename BASE>
class TheClass : public BASE {
/********************************************************************************************/
// CTor / DTor //
/********************************************************************************************/
public:
template <typename... ARGS>
explicit TheClass(ARGS&&... args)
: BASE(std::forward<ARGS>(args)...)
{
}
1

does it in last 2018 version as well

1
Avatar
Permanently deleted user

Just as a hint:

I had the same issue but only one one project.

I found out that it was my own fault: I had am #include dependency loop (the included file included my file). Really lazy error.

But CLion heated my computer in trying to resolve, instead of just telling me. Could be a good Change Request to have Lion indicate that kind of problem, which easily happens when merging projects. 

0

Please sign in to leave a comment.