CLion 2019.1.2 critical bug-fix update


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.


Your CLion Team
The Drive to Develop

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

19 Responses to CLion 2019.1.2 critical bug-fix update

  1. Rogiel Sulzbach says:

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

    • Rogiel Sulzbach says:

      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.

  2. Ernst Maurer says:

    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…

  3. John says:

    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(
    at com.jcraft.jsch.agentproxy.Buffer.getShort(
    at com.jcraft.jsch.agentproxy.Buffer.getInt(
    at com.jcraft.jsch.agentproxy.Buffer.getString(
    at com.jcraft.jsch.agentproxy.AgentProxy.getIdentities(
    at com.jcraft.jsch.agentproxy.RemoteIdentityRepository.getIdentities(
    at com.pastdev.jsch.DefaultSessionFactory.setDefaultIdentities(
    at com.pastdev.jsch.DefaultSessionFactory.(
    at com.pastdev.jsch.DefaultSessionFactory.(
    at com.pastdev.jsch.nio.file.AbstractSshFileSystem.(
    at com.pastdev.jsch.nio.file.UnixSshFileSystem.(
    at com.pastdev.jsch.nio.file.UnixSshFileSystemProvider.newFileSystem(
    at com.intellij.ssh.nio.UnixSshFileSysProviderInternal.newFileSystem(
    at com.intellij.ssh.nio.UnixSshFileSysProvider.newFileSystem(
    at com.jetbrains.cidr.system.RemoteHost.(
    at com.jetbrains.cidr.cpp.toolchains.CPPEnvironment.a(
    at com.jetbrains.cidr.cpp.toolchains.CPPEnvironment.(
    at com.jetbrains.cidr.cpp.toolchains.CPPEnvironment.(
    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$
    at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(
    at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(
    at com.jetbrains.cidr.cpp.toolchains.CPPToolchainsPanel$ToolchainPanel$addChecker$runnable$1$run$
    at com.intellij.util.concurrency.QueueProcessor.runSafely(
    at com.intellij.util.Alarm$Request.runSafely(
    at com.intellij.util.Alarm$
    at java.util.concurrent.Executors$
    at com.intellij.util.concurrency.SchedulingWrapper$
    at com.intellij.util.concurrency.BoundedTaskExecutor.doRun(
    at com.intellij.util.concurrency.BoundedTaskExecutor.access$100(
    at com.intellij.util.concurrency.BoundedTaskExecutor$2.lambda$run$0(
    at com.intellij.util.ConcurrencyUtil.runUnderThreadName(
    at com.intellij.util.concurrency.BoundedTaskExecutor$
    at java.util.concurrent.ThreadPoolExecutor.runWorker(
    at java.util.concurrent.ThreadPoolExecutor$

  4. Helge Penne says:

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

    This needs an urgent fix!

  5. Sigurd Pleym says:

    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 ?

  6. 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.

Leave a Reply

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