CLion 2018.1.1 EAP

Posted on by Anastasia Kazakova

We are glad to announce the start of Early Access Preview for CLion 2018.1.1, a bug-fix update to the recently released major CLion update. Build 181.4445.17 is now available.

Please, note that this EAP build requires an active subscription (or you can start a 30-day evaluation period).

Download CLion 2018.1.1 EAP

  • C++ support

    The biggest improvement is a fix for CPP-12079 and related issues:

    • Incorrect parsing of unordered_map
    • Incorrect resolving of shared_ptr with a forward declaration
    • Incorrect parsing of unique_ptr in some cases
    • Incorrect red code highlighting in projects with libxml2
    • And some more similar and duplicated issues linked to it in our tracker
  • WSL-related issue, when the CMake project loading can take forever (CPP-12519), was addresses in this EAP build.
  • This build fixes a couple of cases when “Typeahead timeout is exceeded” exception was caught (IDEA-187808).
  • GDB debugger

    There us a bunch of issues fixed there. The main one is related to STL containers that were not updated during stepping, if the breakpoint was set before the containers were filled (CPP-7166, CPP-7574, CPP-7720).

Full release notes are available by the link. And to learn about our roadmap for CLion 2018.2 read this blog post.

Your CLion Team

JetBrains
The Drive to Develop

Comments below can no longer be edited.

22 Responses to CLion 2018.1.1 EAP

  1. Tano says:

    April 2, 2018

    Hi Anastasia, can you explain please what this action.aware.typeAhead does?
    Because it seems that it’s not fixed in this EAP and I want to keep it disabled from the Registry.
    Thanks

    • Anastasia Kazakova says:

      April 2, 2018

      If it’s not fixed, then, please, describe the detailed scenario (what you do to get the issue), because seems we failed to reproduced your case. All cases that we managed to reproduce are covered in this build.

      • Tano says:

        April 3, 2018

        I already did 2 weeks ago(see my post on 22 Mar 2018 15:00, although it seems that google deleted my old video), I just open the Find in Path and the “Text to Find” edit box just freezes for 5-6 seconds, I cannot type anything, even if I press the keys. Then I get the error in the lower-right of the screen.

        See video: https://photos.app.goo.gl/wr047HIITUU6j0so1

        Is it clear now?

        • Tano says:

          April 3, 2018

          I attached a higher quality video on the bug’s page. (IDEA-187808)

        • Anastasia Kazakova says:

          April 3, 2018

          Thanks for the video. We’ll continue the investigation.

  2. mbalabin says:

    April 3, 2018

    Great thanks to Eldar Abusalimov for his work on GDB issues!

    • Eldar Abusalimov says:

      April 4, 2018

      You’re very welcome, and thanks for the issues you report on the tracker!

  3. Tano says:

    April 9, 2018

    Anastasia, are there any news about Find in Path dialog? You told me in the past that a redesign is in progress because of the several bugs posted and because it’s less usable in some cases compared to the old versions.
    Some of them IDEA-170658, IDEA-170662, IDEA-170156, IDEA-176371 (this is closed but it’s not fixed), IDEA-172930

    Thank you

    • Anastasia Kazakova says:

      April 9, 2018

      I have no additional info about these for now. I know some adjustments are still in plans, but you’d better ping the developers in the corresponding tickets if you need a quicker answer, I’m afraid I have no extra information and can only ping there on my own.

      Which one if the most crucial for you?

      • Tano says:

        April 10, 2018

        Thank you, I don’t know what developer is in charge of them, because all CLion developers are amazed “Are you using the old dialog? But why?”
        Because the new one is full of bugs, doh…:))

        I gave the new Find a new chance today and I found new 2 bugs in 5 minutes :))))
        CPP-12656
        CPP-12657

        It’s nothing crucial for me, but please do not drop the old dialog, until all of the new ones are fixed.

        For me it’s important to fix CLion problems with symlinks, because CLion does not handle them properly (example: CPP-12309)

        Thanks

  4. Denis Marinov says:

    April 10, 2018

    Which compiler takes less time to compile in CMake? I’m using MinGW64 and it takes up to 2 and an half seconds to compile and run the code for each test. Thank you!

    • Anastasia Kazakova says:

      April 10, 2018

      You might be interested in this comparison: https://insights.dice.com/2013/11/26/speed-test-2-comparing-c-compilers-on-windows/

      • Denis Marinov says:

        April 11, 2018

        Hi Anastasia,

        Thank you for this article. I’ll test some of the listed compilers on my machine to determine which one to stick with. I’m currently using Microsoft C++ Compiler and it’s not bad, but I’ll see.

        • Anastasia Kazakova says:

          April 11, 2018

          There is also the thing called incredibuild that works with CMake and speeds up the compile process. You might try it as well. Also, for MSVC we use NMake generator in CMake which it probably not the quickest one, but unfortunately the only one supported for now

          • Denis Marinov says:

            April 11, 2018

            I’m not sure how incredibuild works. Are there any tutorials on how to implement it with Clion/CMake, found only for VS?

            It happens that GCC is quite preferable by other developers. But than again by installing the MSVC Build Tools I can use it in Rider as well. Sadly it takes up to 6 GB disk space.

            • Anastasia Kazakova says:

              April 11, 2018

              There is no special integration, but it simply works with CMake. So you can just build using it, independently of CLion.

          • Denis Marinov says:

            April 11, 2018

            Okay, thank you. I’ll give it a try later. Keep up with the good work!

            • Anastasia Kazakova says:

              April 11, 2018

              Thanks!

  5. J. says:

    April 12, 2018

    The download button points to the page saying “EAP builds have been moved to the site for easier search. This confluence page is now obsolete.”
    Where we can directly download EAP now? Toolbox app is not an option.

  6. Victor Sergienko says:

    April 16, 2018

    Came here today to express my concern with C++ parser performance in 2018.1.
    I’m afraid that there’s something fundamentally wrong with it, if changing a method signature kicks my laptop’s fans up for 2 minutes, and syntax errors are not cleared till fans settle back.
    Autocompletion speed is still a disaster, I always type .c_str() faster than autocompletion pops up. Except for the times where a parser is running, and it doesn’t pop up at all.
    That’s on a relatively small project (under 1000 files) where the only templates are STL.

    • Anastasia Kazakova says:

      April 18, 2018

      We can handle you concern better if you provide CPU snapshots. But I guess you’ve already done in YT, if not – please do, this will really help.

      In general, we do work constantly on performance. And we have a huge plan how to overcome current issues.
      At the same time, many things in parser were fixed and improved in 2018.1, which unfortunately led to some extra degradations, as some more accurate parsing is now happening and takes longer.

      However, we hope that at least typing and highlighting freezes will be eliminated soon. And then we’ll move to completion and the rest. Stay tuned. And thanks for the fair feedback.

Subscribe

Subscribe for updates