CLion 2019.3.1 Critical Bug-fix Update

Last week we released CLion 2019.3. Unfortunately, it was affected by several unpleasant issues. We’ve investigated all the reports from our users and promptly addressed the discovered problems.

CLion 2019.3.1 (build 193.5233.144) is now available for download from our website, via the Toolbox App, or via snap (for Ubuntu). A patch update will be available shortly.


This update contains the following fixes:

  • Language engine:
    • A problem with randomly occurring red code and an incorrect suggestion to import user classes from the std namespace turned out to be an issue with the missing include file (CPP-18270 and the related CPP-18246, CPP-18247CPP-18280).
    • Completion of standard library symbols in the global namespace is now working correctly in Clangd (CPP-18249).
    • Various fixes preventing the Clangd-based engine from crashing were introduced.
  • Remote development:
    • A mechanism of synchronizing headers in background was recently enabled by default, and it turned out to cause massive delays on loading CMake projects in many cases (e.g. CPP-18277). We’ve reverted it for now until we can come up with a better solution.

Our team appreciates all the valuable feedback the community provided after the release and sincerely apologizes for any inconvenience caused.

Your CLion Team
The Drive to Develop

This entry was posted in Announcement and tagged , , . Bookmark the permalink.

25 Responses to CLion 2019.3.1 Critical Bug-fix Update

  1. Matt Hurd says:

    Good news is that clangd crashes are less frequent. Not so good news is that some parsing and erroneous error reporting continues (ranges v3 & macros). –Matt See updated with a newer screenshot.

  2. Nejc Zdovc says:

    Switcher is still broken. If you press ctr + tab on macos to open swithcer it will jump to third item and not a second one as it show. Because of that it’s impossible to quickly switch between current and previous file

  3. This update makes remote development possible again. Thanks for the quick fix.

  4. Steve says:

    This change actually broke remote development for me. When I switch branches in git the changes don’t get synchronized on the remote machine and it tries compiling the old version of the files.

  5. Gary says:

    I am using CLion 2019.3.1 on a Mac running Mojave. When I delete a file from my local file system (right click -> delete), I am no longer prompted to remove the file from the remote SVN repo. I checked my settings and it appears to me that I should still be prompted to remove the file from the remote SVN repo. The effect is that when I go to commit the delete change, I am no longer able to commit the delete change to the remote SVN repo.

  6. Gary says:

    On second thought, my problem is the regression that you asked me about and more. After I delete files, I don’t see the files to delete from the SVN repo in the Commit Changes dialog. This is the case if the change set is only deleted files and when there is a mixture of deleted files and modified files. This problem did not occur in any of the versions from 2018.1 through 2019.2.

Leave a Reply

Your email address will not be published. Required fields are marked *