IntelliJ IDEA 2018.2.1 Update Available

Hooray!

If you haven’t yet updated your IntelliJ IDEA to v2018.2 (release a couple of weeks ago),  there’s no excuse to wait any longer. Why? Because we’ve just released  IntelliJ IDEA 2018.2.1. This fresh update brings important bugfixes and improves performance in a number of areas.

Here’s a quick list of the most important changes:

  • Fixed poor performance of VCS repository detection (related to symlinks)
  • Fixed broken Android Profiler
  • Fixed poor performance experienced when working with Spring projects
  • Added support for Java 9‘s –upgrade-module-path option
  • Improved support for Groovy 3 syntax
  • Updated bundled TypeScript to v3
  • Minor JavaScript/TypeScript improvements
  • Minor Spring Boot and Spring Integration bugfixes
  • And many more — please see the release notes

Would you like to manage your IDE updates and projects easier? Make sure to try Toolbox App. This tiny tray application will help you keep all JetBrains IDEs and your projects in one place.

P.S.: Have any feedback or found a bug or a performance issue. Please report it to our issue tracker. This will help make the IDE better!

The JetBrains Team
“The Drive to Develop”

About Andrey Cheptsov

Part-time dreamer. JVM/JavaScript geek. IntelliJIDEA Marketing Manager at JetBrains.
This entry was posted in Releases and tagged , . Bookmark the permalink.

8 Responses to IntelliJ IDEA 2018.2.1 Update Available

  1. Matthew Burghoffer says:

    I don’t know if anyone else has experienced this – but with this release, any time I type even a single character into a build.gradle file, the memory usage and cpu usage spike, and the IDE becomes frozen for about 15-30 seconds. No error messages are recorded. After the wait, the IDE returns to normal (unless I write a single character into build.gradle again). Any idea for troubleshooting?

  2. Mike says:

    2018.2.1 has major problems (Mac OS version). How to I downgrade to 2018.2?

    2018.2.1 keeps locking up (buttons stop responding, can still move dialog windows but no interface elements respond). I have to Force Quit the app, then when I restart I have to import my project like it is brand new even though the intellij .idea directory is there.

  3. Matt says:

    2018.2.1 used all the CPUs on my MacBook Pro for half an hour before I killed it off and went back to 2018.1.6. Something is very broken with this release.

  4. Didier Martin says:

    Hello,

    Installing this update failed to me. 2018.2.1 build 182.3911.43. When I try to apply this update, a window appear with named “Some conflicts were found in the installation area”, then there is a list of processes .jar that the tools should “kill” to perform the update.

    When I click on “proceed”, the message “An error occurred when preparing the patch: NullPointerException: null” appears.

    In the log file, I can see the lines below :

    09/08 21:27:16 INFO Runner.cleanup – Cleaning up…
    09/08 21:27:16 INFO Utils.tryDelete – deleted: C:\Users\PC1\.PhpStorm2018.2\system\log\idea.updater.files.8943590811843766712\patch.tmp.0
    09/08 21:27:16 INFO Utils.tryDelete – deleted: C:\Users\PC1\.PhpStorm2018.2\system\log\idea.updater.files.8943590811843766712
    09/08 21:27:16 INFO Utils.cleanup – deleted working directory: C:\Users\PC1\.PhpStorm2018.2\system\log\idea.updater.files.8943590811843766712
    09/08 21:30:13 INFO Runner.initLogger – — Updater started —
    09/08 21:30:13 INFO Runner.main – args: [install, C:\Program Files\JetBrains\PhpStorm 2018.1.2]
    09/08 21:30:13 INFO Runner.main – destFolder: C:\Program Files\JetBrains\PhpStorm 2018.1.2, case-sensitive: false
    09/08 21:30:14 INFO Utils.getTempFile – created working directory: C:\Users\PC1\.PhpStorm2018.2\system\log\idea.updater.files.5411800145483106644
    09/08 21:30:14 INFO Runner.install – Extracting patch file…
    09/08 21:30:14 INFO Utils.getZipEntry – entryPath: patch-file.zip
    09/08 21:30:14 INFO Utils.getZipEntry – entryPath: .patch-info
    09/08 21:30:14 INFO PatchFileCreator.prepareAndValidate – PhpStorm (build 182.3684.42) -> PhpStorm (build 182.3911.43)
    09/08 21:30:14 INFO Patch.forEach – Validating installation… [221 actions]
    09/08 21:31:34 ERROR Runner.install – prepare failed
    java.lang.NullPointerException
    at com.intellij.updater.NativeFileManager$Process.terminate(NativeFileManager.java:57)
    at com.intellij.updater.PatchAction.lambda$shouldApply$0(PatchAction.java:127)
    at java.lang.Iterable.forEach(Iterable.java:75)
    at com.intellij.updater.PatchAction.shouldApply(PatchAction.java:127)
    at com.intellij.updater.Patch.apply(Patch.java:311)
    at com.intellij.updater.PatchFileCreator.apply(PatchFileCreator.java:78)
    at com.intellij.updater.Runner.install(Runner.java:313)
    at com.intellij.updater.Runner.main(Runner.java:109)

    What’s happening ? Could you help ?

    In advance, thank you.

  5. Not Mike says:

    2018.2.1 on Windows 10 has bad GDI type leaks where the window elements start redrawing incorrectly and eventually stops responding to input (or the input elements aren’t where they are drawing).

  6. Devesh says:

    2018.2.1 Mac OS version – Debugger is not working

  7. pritesh ranjan says:

    i am using gradle 1.2 with latest intellij community version. But build is failing in intellij with below error. please provide some help.

    Unable to load class ‘org.gradle.tooling.provider.model.ToolingModelBuilder’.
    Possible causes for this unexpected error include:Gradle’s dependency cache may be corrupt (this sometimes occurs after a network connection timeout.)
    Re-download dependencies and sync project (requires network)The state of a Gradle build process (daemon) may be corrupt. Stopping all Gradle daemons may solve this problem.
    Stop Gradle build processes (requires restart)Your project may be using a third-party plugin which is not compatible with the other plugins in the project or the version of Gradle requested by the project.In the case of corrupt Gradle processes, you can also try closing the IDE and then killing all Java processes.

Leave a Reply

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