text: A new bug-fix update CLion 2018.1.2, build 181.4668.70, is now available for download.
  Patches from v2018.1.1 will be available shortly. You can also install it using Toolbox App or snap packages if you are on Ubuntu.
  If you are using CLion v2018.1, mind that automatic update notification doesn’t appear due to technical issue. Please use the Check for updates action manually (Help | Check for Updates… on Windows/Linux or CLion | Check for Updates… on macOS).
  This update fixes a few regressions and addresses several issues related to
  using keyword:
  - A combination of
  usingand void template argument caused an incorrect “Too many template arguments, expected 0” error. Typical sample is
  futureusage.
  - Incorrect handling of forward declared default template parameters inside namespace with
  using, which leads to false “Too few template arguments” error (CPP-10477).
  - Another false “Too few template arguments” error in case of
  usingtemplate with function decomposition (CPP-9604).
  Besides, CLion 2018.1.2 fixes incorrect highlighting for gmock. Google C++ Mocking Framework is widely used for the unit testing. Previous CLion versions had some issues with parsing mocked methods with arguments (CPP-3415). Now these issues are mostly fixed.
  Full release notes are available here.
  Your CLion Team
  JetBrains
  The Drive to Develop
  Unfortunately, it appears with every release you are breaking something new. 2018.1.1 I would get false errors. Clion would highlight errors in code that weren’t actual errors. I could usually fix this by resaving the file. Now it’s giving me errors with template parameters in lambda expressions. Even though it compiles without issue and all test cases work correctly. This bit of code gets highlighted as an error in Clion 2018.1.2, but doesn’t in 2018.1.1.
  e->addComponent(
  [](MockComponentOne* c){
  c->x(12.0);
  c->y(4.0);
  });
  It says there’s a type mismatch between std::function and std::function. The actual function signature is ‘template Status addComponent(std::function init);’
  I’m starting to become disappointed in the quality of this product. It’s been a solid product in the past, but lately, it seems the quality has been suffering. Please fix. I really like Clion and don’t want to switch.
  We are sorry for the inconvenience. We are constantly working hard on improving the product and sometimes, unfortunately, regression testing doesn’t catch things. We’ll take a look at your problem.
  By the way, which compiler is that (with version)? I guess this is the full sample?
  Yes, that’s the sample. Thanks for looking into it. I’m Using WSL with Ubuntu 16.04.4 LTS. GNU Make 4.1, CMake 3.5.1, c++/cc 5.4.0, gdb 7.11.1.
  yes, it’s a regression with gcc and std::function. Currently under development/testing:
  Should be fixed in this update:
  Will there be more bug fix updates to 2018.1? It will regularly freeze up completely for several minutes at a time (100% load on one core only), seemingly while doing parsing or symbol lookup (this has been a problem with both 2018.1, 2018.1.1 and 2018.1.2).
  This is so bad that we’ve had to avoid this version and stay on 2017.3. I was hoping that CLion would get increasingly better at parsing and symbol lookup, but sadly it seems that this is not the case. I hope this improves. We like CLion a lot, but the current state of 2018 makes it impossible to use.
  One reason for performance degradation in 2018.1.2 is here. And we are currently discussing the possibility for backporting to some 2018.1.x.
  Just to check if that’s the same issue for you – can you please report the thread dumps (created automatically on freeze in the log directory) to us?
  My issue might not be CPP-12837, as my steps to reproduce are different. Is it OK if I file this as a new defect, and link from CPP-12837 to the new one in case they are the same root cause?
  Sure
  Filed as
  We’ll check, thanks. There are more performance fixes in 2018.1 coming soon as 2018.1.3. Hopefully today
  CLion 2018.1.3:
  I’ve also noticed unprecedented FULL HANGS in latest Clion.. Never expected such behaviour from such IDE.. Though both CPU and hdd are idle ALL Clion GUI hangs even mouse cursor is missing when inside Clion’s window…
  Could you please check the tread dumps in the log directory generated automatically?
  Where do I post you those logs as a zip archive? There used to be your ftp but I can’t find it…
  Please find the information in the end of the article here:
  Please check the 2018.1.3 update with some important performance fixes: