CLion 2019.1.3 update


Please welcome a new bug-fix update: CLion 2019.1.3! Build 191.7141.37 is now available to download from our website, via the Toolbox App, or via snap (for Ubuntu). A patch-update will be available shortly.


Here are the highlights:

  • CLion can now work with header guards that use several define patterns (CPP-15736).
  • CMake 3.14.3 is now bundled.
  • The exception, when Google Sanitizers were launched from CLion, is fixed.

Full release notes are here.

Your CLion Team
The Drive to Develop

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

33 Responses to CLion 2019.1.3 update

  1. llvim says:

    clion freeze a lot on my mac when update to 2019.1

    • Anastasia Kazakova says:

      When UI is freezing, there are thread dumps generated automatically in logs directory (Help | Show Logs in Finder). Please pack some fresh dumps and send to our support ( for further investigation.

  2. Sergey says:

    Hello. After i call hierarchy from action menu (Command+Shift+A), this command no longer works.
    Example output:
    ditto(1) – copy directory hierarchies, create and extract archives
    find(1) – walk a file hierarchy
    hier(7) – layout of filesystems
    iwidgets_hierarchy(n), iwidgets::hierarchy(n) – Create and manipulate a hierarchy widget
    mdimport(1) – import file hierarchies into the metadata datastore
    mtree(8) – map a directory hierarchy
    pax(1) – read and write file archives and copy directory hierarchies
    torque(1) – ./” ./” Launches one or more child processes, each of which performs a series of bandwidth intensive operations, and after completion reports the bandwidth actually achieved by each operation during a period when all operation streams were executing simultaneously. ./” ./”
    ttk::treeview(ntcl) – hierarchical multicolumn data display widget

  3. Sergey says:

    When i press again this shortcut i see console popup from this message, but i can call action menu again only after restart clion

  4. Yuriy says:

    I tried to evaluate again, and it still is not usable for my main project :( too slow debugger. After stopping at first breakpoint it thinks for a minute or even longer before I can do any other action. This doesn’t happen in Xcode. All tips from how to enhance debugging experience don’t help, i turned off all data views & renderers .. no luck.
    If you are patient enough though after this first giant delay it works well without slowness, but the time is big enough in Xcode I relaunch program several times …

  5. Tano says:

    Hi Anastasia, when can we expect 2019.2 EAP? I write a lot of CMake lately and CPP-15515 is killing me, it’s a bad coincidence.:)

    • Anastasia Kazakova says:

      Should start soon in May, however I can’t provide any more exact estimate on this for now.

  6. Alexander says:


    Do the CLion developers regularly test Qt-based projects?
    It seems that there’s always something that’s broken in Qt-using code.

    For example, in the current release, QStringLiteral(“”) says “Use of undeclared identifier ‘QStringLiteral'”.
    If I disable clangd server, QStringLiteral itself is no longer red, but using raw string literals inside it produce this error: “Error after macro substitution: Incompatible types in initializer: Initializer string is too long for array of chars.”

    Note that there are quite a few other nonsensical errors with clangd – see the example project I’m linking to.

    Unfortunately, stuff like this makes the IDE really hard to use – the whole file is highlighted with red squiggles.

    Here is a dead-simple example project (see main.cpp for QStringLiteral, main_window.cpp for other nonsensical errors with clangd):


    • Anastasia Kazakova says:

      We do check various projects in tests and in manual smoke tests before publishing the build. We’ll see what’s going on for the Qt code there, thanks.

      On which environment/platform/toolchain are you?

    • Anastasia Kazakova says:

      We actually failed to reproduce the problem with clangd enabled (checked clang and gcc). So it would be useful to know your toolchain and environment.
      With clangd disables looks similar to and But should be eliminated with clangd on. Let’s investigate the issue with clangd enabled first.

      • Alexander says:

        Hi Anastasia,

        Thanks a lot for the investigation. For now I enabled clangd.

        CLion settings:

        These are my platform details:
        OpenSUSE Linux 15.0.
        gcc-7-lp150.1.50.x86_64 (system-bundled),
        gcc8-8.3.1+r269383-lp150.67.1.x86_64 (from OBS),
        clang7-7.0.1-lp150.24.2.x86_64 (from OBS),
        glibc-2.26-lp150.11.9.1.x86_64 (system-bundled),
        libqt5-qtbase-devel-5.9.4-lp150.4.8.x86_64 (system-bundled).

        The opensuse-bundled gcc 7 is the system compiler. Switching to a clang-based toolchain doesn’t affect the errors – they’re still there.

        Control-clicking “QStringLiteral” actually takes me to qstring.h, where no errors are highlighted. Makes me wonder why it’s “undeclared” if clion finds it.

        I tried with a clean CLion configuration – the errors are still there.

        Maybe it’s related to the Qt version (5.9.4)? I’m using the one supplied with the distribution – can’t upgrade it without upgrading KDE as well.


  7. rose says:

    can i install on win 10 64bit?

  8. Tano says:

    Sorry Anastatis, CLion is very very slow, every year you told us that it’s fast but it is not, when I keep press Enter, I have small delays, posted like 3-4 bugs about this, everytime you guys “fix” the bugs but is not fixed…now CMake is also slow…CPP-16207

    • Tano says:


    • Anastasia Kazakova says:

      We are sorry to hear that. We work constantly on performance improvements and there are lots of changes in this direction. Hope it will improve in your case as well soon.
      We’ll investigate the CMake lag and update you in the ticket.

      • Tano says:

        Thanks, I barely convinced 2 colleagues to start using CLion and after 2 days full of laggy typing they switched back to Eclipse .. please note that we use i7 and 32gb ram and the project is not large, 100k LOC

  9. jolia says:

    hi i use win 7 can i install?

Leave a Reply

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