CLion 2019.1.2 critical bug-fix update

Posted on by Anastasia Kazakova

Hi,

A few days ago we published the first bug-fix update (2019.1.1) for the recently released CLion 2019.1. Thanks to our vigilant users, we’ve learned quickly that this build is affected by a very unpleasant freeze on IDE start when several projects are opened (CPP-16039, OC-18440). The IDE fails to recover in that case, unfortunately.

We are sincerely sorry for this and apologize for any inconvenience it might have caused. We’ve analyzed the source of the issue and will do our best to prevent such situations in the future.

If you are using v2019.1 (and especially 2019.1.1), we recommend that you update to the newest 2019.1.2 build, which is now publicly available. Download it from our website, via the Toolbox App, or via snap (for Ubuntu). A patch-update will be available shortly.

DOWNLOAD CLION

Your CLion Team
JetBrains
The Drive to Develop

Comments below can no longer be edited.

19 Responses to CLion 2019.1.2 critical bug-fix update

  1. Rogiel Sulzbach says:

    April 22, 2019

    Has the fix for CPP-15464 been included in this build as well?

    • Rogiel Sulzbach says:

      April 22, 2019

      Never mind. It appears to have shipped with 2019.1.1.

      Weird. I was pretty sure I saw that problem yesterday while working under Windows. Next time I boot into Windows I’ll check this.

      • Anastasia Kazakova says:

        April 22, 2019

        Sure, let us know if you see the problem back. It should be fixed, but maybe we missed some case.

        • Rogiel Sulzbach says:

          April 29, 2019

          @Anastasia, I have managed to reproduce this issue and it is still occurring in 2019.1.2.

          See CPP-16135

          • Anastasia Kazakova says:

            April 30, 2019

            Thanks for the detailed ticket. We are on it.

  2. Ernst Maurer says:

    April 26, 2019

    clangd makes 99% load of CPU 🙁
    in addition, I suppose, clangd generates .pch files (in system temp) which ones take a tens of GBs on the drive…

    • Ernst Maurer says:

      April 26, 2019

      by the way, all it works extremely slow, even the typing requires 1-2 sec pauses between words

      • Anastasia Kazakova says:

        April 28, 2019

        That doesn’t seem like a normal situation. Can you please send idea.log (Help | Show log) to our support: clion-support@jetbrains.com. Also, CPU snapshot might be useful, because lag on typing might be completely unrelated to clangd: https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems

        • Ernst says:

          April 30, 2019

          appologizes that didn’t respond on that moment, but I was looking for any solution to continue the work.
          for me, this case solved the problem : I switched on your own language server and was working a couple of days( and also cleaned up a temporaries of clangd), a day ago I tried to switch on clangd again, and currently don’t see the problem, no lags and no drain of drive space.
          I’ll provide you with a logs in case of this issue will be again

          • Anastasia Kazakova says:

            April 30, 2019

            Great, thanks for coming back with the reply. Let us know if you can reproduce the problem again

  3. John says:

    April 30, 2019

    Failure to configure remote host, can’t save config, log:

    2019-04-30 13:02:18,645 [ 415392] ERROR – llij.ide.plugins.PluginManager – CLion 2019.1.2 Build #CL-191.6707.69
    2019-04-30 13:02:18,645 [ 415392] ERROR – llij.ide.plugins.PluginManager – JDK: 1.8.0_202-release; VM: OpenJDK 64-Bit Server VM; Vendor: JetBrains s.r.o
    2019-04-30 13:02:18,646 [ 415393] ERROR – llij.ide.plugins.PluginManager – OS: Windows 10
    2019-04-30 13:02:18,646 [ 415393] ERROR – llij.ide.plugins.PluginManager – Last Action: EditorPaste
    2019-04-30 13:02:18,944 [ 415691] INFO – dev.jsch.DefaultSessionFactory – An AgentProxy Connector was found, check for identities
    2019-04-30 13:02:18,946 [ 415693] ERROR – til.concurrency.QueueProcessor – 1024
    java.lang.ArrayIndexOutOfBoundsException: 1024
    at com.jcraft.jsch.agentproxy.Buffer.getByte(Buffer.java:142)
    at com.jcraft.jsch.agentproxy.Buffer.getShort(Buffer.java:138)
    at com.jcraft.jsch.agentproxy.Buffer.getInt(Buffer.java:123)
    at com.jcraft.jsch.agentproxy.Buffer.getString(Buffer.java:181)
    at com.jcraft.jsch.agentproxy.AgentProxy.getIdentities(AgentProxy.java:112)
    at com.jcraft.jsch.agentproxy.RemoteIdentityRepository.getIdentities(RemoteIdentityRepository.java:47)
    at com.pastdev.jsch.DefaultSessionFactory.setDefaultIdentities(DefaultSessionFactory.java:273)
    at com.pastdev.jsch.DefaultSessionFactory.(DefaultSessionFactory.java:89)
    at com.pastdev.jsch.DefaultSessionFactory.(DefaultSessionFactory.java:71)
    at com.pastdev.jsch.nio.file.AbstractSshFileSystem.(AbstractSshFileSystem.java:53)
    at com.pastdev.jsch.nio.file.UnixSshFileSystem.(UnixSshFileSystem.java:34)
    at com.pastdev.jsch.nio.file.UnixSshFileSystemProvider.newFileSystem(UnixSshFileSystemProvider.java:359)
    at com.intellij.ssh.nio.UnixSshFileSysProviderInternal.newFileSystem(UnixSshFileSysProviderInternal.java:54)
    at com.intellij.ssh.nio.UnixSshFileSysProvider.newFileSystem(UnixSshFileSysProvider.java:30)
    at com.jetbrains.cidr.system.RemoteHost.(RemoteHost.java:71)
    at com.jetbrains.cidr.cpp.toolchains.CPPEnvironment.a(CPPEnvironment.java:75)
    at com.jetbrains.cidr.cpp.toolchains.CPPEnvironment.(CPPEnvironment.java:61)
    at com.jetbrains.cidr.cpp.toolchains.CPPEnvironment.(CPPEnvironment.java:50)
    at com.jetbrains.cidr.cpp.toolchains.CPPToolchainsPanel$ToolchainPanel$12.readAndCheckVersion$intellij_clion(CPPToolchainsPanel.kt:735)
    at com.jetbrains.cidr.cpp.toolchains.CPPToolchainsPanel$ToolchainPanel$12.readAndCheckVersion$intellij_clion(CPPToolchainsPanel.kt:724)
    at com.jetbrains.cidr.cpp.toolchains.VersionChecker.check(CPPToolchainsUIUtils.kt:95)
    at com.jetbrains.cidr.cpp.toolchains.CPPToolchainsPanel$ToolchainPanel$addVersionChecker$checkerRunnable$1.runInBackground(CPPToolchainsPanel.kt:983)
    at com.jetbrains.cidr.cpp.toolchains.CPPToolchainsPanel$ToolchainPanel$addVersionChecker$checkerRunnable$1.runInBackground(CPPToolchainsPanel.kt:977)
    at com.jetbrains.cidr.cpp.toolchains.CPPToolchainsPanel$ToolchainPanel$addChecker$runnable$1$run$1$backgroundFunction$1.invoke(CPPToolchainsPanel.kt:1188)
    at com.jetbrains.cidr.cpp.toolchains.CPPToolchainsPanel$ToolchainPanel$addChecker$runnable$1$run$1$backgroundFunction$1.invoke(CPPToolchainsPanel.kt:1161)
    at com.jetbrains.cidr.cpp.toolchains.CPPToolchainsPanelKt$sam$java_lang_Runnable$0.run(CPPToolchainsPanel.kt)
    at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:586)
    at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:532)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:86)
    at com.jetbrains.cidr.cpp.toolchains.CPPToolchainsPanel$ToolchainPanel$addChecker$runnable$1$run$1.run(CPPToolchainsPanel.kt:1190)
    at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:232)
    at com.intellij.util.Alarm$Request.runSafely(Alarm.java:368)
    at com.intellij.util.Alarm$Request.run(Alarm.java:355)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at com.intellij.util.concurrency.SchedulingWrapper$MyScheduledFutureTask.run(SchedulingWrapper.java:224)
    at com.intellij.util.concurrency.BoundedTaskExecutor.doRun(BoundedTaskExecutor.java:220)
    at com.intellij.util.concurrency.BoundedTaskExecutor.access$100(BoundedTaskExecutor.java:26)
    at com.intellij.util.concurrency.BoundedTaskExecutor$2.lambda$run$0(BoundedTaskExecutor.java:198)
    at com.intellij.util.ConcurrencyUtil.runUnderThreadName(ConcurrencyUtil.java:224)
    at com.intellij.util.concurrency.BoundedTaskExecutor$2.run(BoundedTaskExecutor.java:194)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)

    • Vasily Romanikhin says:

      April 30, 2019

      Hello @John

      Could you please create a separate issue, attach this stacktrace and precisely describe “steps to reproduce” and your environment.
      https://youtrack.jetbrains.com/issues/CPP

      Thanks in advance.

      • John says:

        May 6, 2019

        Oh, I found the reason, because I executed pageant.exe.

  4. Helge Penne says:

    May 6, 2019

    CLion 2019 has broken debugging. It no longer stops on breakpoints (both the gdb and llvm debugger).

    This needs an urgent fix!

    https://youtrack.jetbrains.com/issue/CPP-16174

  5. Sigurd Pleym says:

    May 7, 2019

    Hi
    My 2019.1.2 version freezes , I have two projects open and every morning I have to force quit on OSX and restart them. (Build 191.6707.69)

    Do you need any logs ?

    • Anastasia Kazakova says:

      May 7, 2019

      When the freeze happens the thread dumps are generated automatically and are located in logs directory (Help | Show Logs). Please collect and send them to our support: clion-support@jetbrains.com

  6. Jari van den Heuvel says:

    May 8, 2019

    I am not able to open any .h or .cpp files on 2019.1.2.
    However, .JS, .TS, .HTML, .TX,T .CMake and so forth all open as expected.

    Double-clicking a .cpp file will result in the project bar centering on the clicked file, but won’t open it in the editor. Dragging the file won’t work as well.

    Everything works completely fine on 2018.3.4.

    I have reverted back now, because I need to finish a project but I might see if I can update it again and reproduce the same problem. I have collected logs when this happened.

Subscribe

Subscribe for updates