CLion 2019.3 Hits Beta

CLion 2019.3 goes Beta! To install CLion 2019.3 Beta (build 193.5233.10), download it from the website, update from our Toolbox App, get it through a snap package (if you are using Ubuntu), or use a patch update.

DOWNLOAD CLION 2019.3 BETA

The main highlights for this build are:

  • Completion insert handlers were implemented in Clangd-based language engine, which allows functions/methods to be completed with (), namespaces – with ::, and type aliases – with a space at the end, if they have a built-in underlying type:

Insert handlers

  • Remote mode:

    • Full Remote Mode in CLion requires rsync (for macOS/Linux clients) or tar (for Windows clients) installed on a remote machine. CLion now verifies the tool is installed and provides a warning on the corresponding remote toolchain settings page, which clearly states that “rsync/tar is not installed or not available in PATH on remote host”.
    • You can now set a custom GDB debugger in the Remote or WSL toolchain (CPP-17552).
    • Resync with Remote Hosts is now enabled on project reload by default. This allows CLion to synchronize the header search paths from the remote machine to the local host (to resolve the code correctly in CLion) on every project reload. This operation might be time-consuming, but as it runs in the background, it shouldn’t affect CLion’s performance. If you are still experiencing any performance issues, try disabling the clion.remote.resync.system.cache registry option (Help -> Find Action, type Registry).
  • CMake File API, which makes it possible to use various CMake generators like Ninja in CLion, is now supported not only for v3.15, but for any CMake version higher than 3.15.
  • Code coverage now works with a Ninja generator (CPP-17864).
  • This build also brings several fixes to code completion and a fix for the lengthy UI freeze (CPP-17961).

The full release notes are available here.

Your CLion Team,
JetBrains
The Drive to Develop

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

33 Responses to CLion 2019.3 Hits Beta

  1. Tano says:

    Toolbox does not show any CLion update, perhaps it should happen in a few minutes. :-)
    I hope that CPP-17956 will be fixed in final version, it occurs a few times a day, the only solution is to restart CLion.
    Thanks

    • Anastasia Kazakova says:

      Toolbox might take some time to notice the update.

      As for the CPP-17956 – exceptions will be turned off in the release builds. However, to fix the origin, we need to investigate it deeper and maybe get a reproducible sample.

      • Tano says:

        I understand, I just want to mention that never happened in the past and now I have to restart CLion 2-3 times a day because of this problem.

  2. Rogiel Sulzbach says:

    I’m not sure CPP-17741 is fixed (the CMake File API thing for versions later than 3.15). CLion still display the same message about being unsupported and fallbacks for the Makefile generator.

    I’m using CMake 3.16-rc3 with Windows.

    • Rogiel Sulzbach says:

      For some reason, the Toolbox app launched an older CLion version. After the third attempt restarting CLion, it launched the beta.

  3. Fernando Rodriguez says:

    Will Host Mac also be supported for full remote mode?

  4. Alexander Petrov says:

    I see tens of processes running when I reload remote CMake project, most of the processes are Headers Synchronisation (which of course should be spelled with ‘z’)

    • Anastasia Kazakova says:

      Is it local or remote mode?

      • Alexander Petrov says:

        > remote CMake

        • Anastasia Kazakova says:

          So, then it’s indeed the header symnchronization, which naturally happens to allow IDE to resolve the code correctly on a local host. See this part in the blog post above:

          Resync with Remote Hosts is now enabled on project reload by default. This allows CLion to synchronize the header search paths from the remote machine to the local host (to resolve the code correctly in CLion) on every project reload. This operation might be time-consuming, but as it runs in the background, it shouldn’t affect CLion’s performance. If you are still experiencing any performance issues, try disabling the clion.remote.resync.system.cache registry option (Help -> Find Action, type Registry).

          • Alexander Petrov says:

            yes that’s what I did,
            I don’t like to see tons of processes
            thanks

          • Anastasia Kazakova says:

            You can disable, but then have to sync manually to be able to get the updates from the remote machine after the CMake reload.

          • Oliver Stöneberg says:

            I am also seeing this. Appears that it was introduced with this EAP. Didn’t experience it earlier and never with 2019.2. At some point it was over 100 background tasks. Took quite a while for these tasks to go away, but that might be a side effect of CPP-17597.

          • Anastasia Kazakova says:

            The main problem in this WSL related issue is that we failed to reproduce it. We’ll keep thinking and investigating it

  5. Roman Popov says:

    I have a feeling that last EAP and this Beta started hanging way too often. Killed IDE 3 times today :( Attached last logs to CPP-18052

  6. ilya b says:

    I like this new Header/Source action, it feels snappier than previous ‘Related symbols’ action. With ‘Related’ it might take several seconds just to open a header from .cpp, if header is included from many places.

    Unfortunately the gnarliest bug of the release (IDEA-224810) is not fixed. Release notes mention it as fixed, but in fact it’s not.

    Great job anyways, thanks.

  7. Helge Penne says:

    This bug was marked as fixed in this beta, but the Beta still freezes in the same way and with the same log files, so this bug does NOT seem to be fixed. Please reopen and investigate. The freeze is loooong and occurs frequently and will cause grief and annoyance if you release without fixing:
    https://youtrack.jetbrains.com/issue/CPP-17961

    • Anastasia Kazakova says:

      This is weird as the code that produced the freeze was removed. Pls see my request in the comments. We’ll investigate.
      BTW, do you have Clangd engine enabled in CLion’s settings?

      • Helge Penne says:

        Everything “clangd” is enabled i settings. I think you should consider the possibility that the original analysis of my bug report reached the wrong conclusion, and that the freeze was not caused by the issue that you have already fixed. This seems more likely than that there were two bugs that behaved exactly the same way.

      • Helge Penne says:

        It seems that this beta is no better than the previous release in terms of freezes. This bug is now classified as related to bugs reported as far back as in 2018.1, and that are still open.
        Please fix this as soon as possible. I cannot recommend anyone to upgrade to 2019.3 until this bug is fixed. I would advise you against releasing 2019.3 while this bug is still there. CLion will freeze for as much as five minutes, which risks making your customers very angry.

  8. Helge Penne says:

    You currently have 205 open bugs containing the word “freeze”, going as far back as 2014. That is seriously depressing. I would guess that some of these are probably closed, but if you simply continue to allow the list to keep growing then you have no way to known which bugs that need to be fixed, and the quality of your product will spiral out of control and you will never be able to stabilize it properly.

    You need to resolve ALL of these issues, or you will never be able to create a reliable product. By resolve I mean fix the bug, or determine that it is fixed or a duplicate, or decide that it will not be fixed.

    You should seriously consider changing the way to prioritize. You need to get your bug database under control and really start closing issues. If you will forgive my harsh language, your bug database looks like a complete mess. It confirms my suspicion that filing a bug is useless as it will never be fixed that way, and the only way to get any bug fixed it is complain about it publicly here in the comments section. Very sad and frustrating.

    • Anastasia Kazakova says:

      We are sorry you feel this way. We do track all the freezes and fixed quite a bunch of them in 2019.3. Some (especially the one you’ve mentioned) is not yet fixed and requires some bigger architectural changes that are planned but were not delivered in 2019.3. On many projects, the UI freezes were eliminated significantly, but there is still a huge amount of work to be done, you are right, and we definitely plan it with the top priority.

      • Helge Penne says:

        I agree that you have made some important progress, but it is still very frustrating to see a good tool let down by freeze problems that continue to happen for several years.

        The large number of unfixed freeze issues in the bug database really is an indication that you to not have this under control, and that the problem could be on the product management level. You don’t seem to be taking reported bugs seriously enough. UI freezes should simply not happen this often. These bugs should all be classified as “major”, and go to the top of the backlog right away when they are discovered, not left behind to accumulate in the bug database.

        If major refactorings are required and you are unable to do this in a single release cycle, then at least let us have to option to turn off the features the causes the freezes in the mean time. You should not let these freezes continue to happen just because you plan to do refactorings of these parts of the code some time in the future.

        • Anastasia Kazakova says:

          Unfortunately, it’s not always possible to turn the things off that causes the freeze. The often reason is the heavy C++ code resolve which happens in UI thread. One case might cause freezes in different situations, so turning particular features off doesn’t help. Such freezes are of course the top priority for us.

  9. Roman Popov says:

    How can I remove file from Clangd blacklist? Asking here, because forums are silent ..

    https://intellij-support.jetbrains.com/hc/en-us/community/posts/360006607739-How-to-remove-file-from-Clangd-blacklist-

Leave a Reply

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