CLion 2016.1.2 bug-fix update

Hi everyone,

CLion 2016.1.2 bug-fix update (build 145.971) is available for download. If you are running CLion 2016.1, 2016.1.1 or 2016.1.2 Release Candidate, patch-update is available. Wait for the notification or go ahead and click Check for Updates to install the patch right from the IDE.

This update addresses:

  • a set of problems with console output,
  • broken link for using declaration in Quick Documentation pop-up,
  • a parsing error in case of an in loop variable.
  • GDB console blinking problem on Linux – IDEA-153630.

Full release notes can be found by the link.

In addition to the usual functionality fixes, this update contains important fixes for two security issues inside IntelliJ Platform. The vulnerabilities, in various forms, are also present in older versions of the CLion; therefore, patches for those are also available.

Find more information about the issues, the affected versions and ways to update in this special blog post.

It is strongly recommended for all users to install the update as soon as possible.

Note, that in case you are using CLion 1.0 (or any 1.0.x update), you’ll be offered to download CLion 1.1.2. For other releases (1.1, 1.2, 2016.1) a corresponding update is available (1.1.2, 1.2.5, 2016.1.2).

Your CLion Team
JetBrains
The Drive to Develop

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

6 Responses to CLion 2016.1.2 bug-fix update

  1. Olof says:

    Upgrading from 2016.1(.0) to 2016.1.2 broke the MultiMarkdown plugin.

  2. John says:

    Given this fixes security flaws, I would suggest that it be moved to the first article of the blog rather than the 2016.1 update to make it easier for users to discover it.

    • Anastasia Kazakova says:

      Since every customer gets a personal e-mail with the notification in addition to the notification in the IDE and all the builds on the site are updated, there is not much sense in doing this probably.

      • Olof says:

        I’ve read the release notes and I can’t see that this fixes a security issue. Maybe I’m just not understanding it. What is the security issue?

Leave a Reply

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