IntelliJ IDEA 2016.1.1 Update is Out

If you haven’t upgraded to IntelliJ IDEA 2016.1 yet, there is one more reason not to postpone it any longer. Today we’ve released a bugfix update where you’ll find a number of important fixes.

If you are running IntelliJ IDEA 2016.1, go ahead and click Check for Updates to install the patch right from the IDE. Otherwise, you’re welcome to download and install the new version from the website.

As always, we appreciate your feedback here in comments or directly in our issue tracker.

UPDATE: Don’t worry if you notice a confusing message in the Updates dialog saying that you can evaluate the new version for 30 days, or buy a license key or upgrade online. This is a known problem that will go away after you’ve updated.

Develop with pleasure!

 

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

69 Responses to IntelliJ IDEA 2016.1.1 Update is Out

  1. Andrew says:

    Hi!
    Are this update includes fix for clipboard ignoring in Windows?

  2. Dmitriy says:

    I’m getting reports from my team that this update makes IJ start indexing, and it won’t complete.

    • Pete O'Bryan says:

      It hangs on indexing *.sql files. I marked the “Database” directory where I keep *.sql as Excluded, and it stopped trying to index them. That fixed the issue, but of course now I no longer have an integrated view of my sql files.

  3. User says:

    Gradle multi module support is still broken!
    Last time it worked fine was 15.0.5!
    Fix it ASAP!

    • Dominic North says:

      I am also noticing a problem which is possibly related to this. I have a multi-module Gradle project that I created sometime ago in IntelliJ (15, or even 14).

      I have just revisited the project, for the first time since I upgraded to 2016, and find that tests now fail running from the IDE, even setting Gradle | Runner ‘Gradle Test Runner’. The failure is due to resources not being found in the classpath by Spring. This worked fine before the upgrade.

      I should add that I can run the same tests without problem running the Gradle build itself in IntelliJ

      • Dominic North says:

        …. and now I’ve found the answer, which is to remove the (pre-)existing Run Configurations that fail. Having done so, you can create them again run them in JUnit, and they work fine.

  4. Murat Berk says:

    It got slow !!!

    • Andrey Cheptsov says:

      Could you please provide more details, e.g. a CPU snapshot? This will help us fix it sooner.

      • Xiujun says:

        It uses very very slow !!

        • Tefa says:

          I don’t think saying that its “very very slow” helps anyone

          • Dobbo says:

            It’s extremely slow. On 2016.1.2. Laptop with Intel Core i7-3720QM @ 2.60Ghz and 32 GB ram. CPU and memory at roughly 10% utilization respectively. Loading Django in python interpreter (not debug) takes roughly 4.5 seconds to start compared to a few milliseconds before the 2016 build. I also noticed some problems with Python Interpreters getting mixed up (Pycharm using other’s projects environments unexpectedly).

  5. Sathish Dharma says:

    Unable to compile java classes. It’s throwing Stack Overflow error.
    Information:Using javac 1.8.0_51 to compile java sources
    Information:java: The system is out of resources.
    Information:java: Consult the following stack trace for details.
    Information:java: at com.sun.tools.javac.util.Position$LineMapImpl.build(Position.java:153)
    Information:java: at com.sun.tools.javac.util.Position.makeLineMap(Position.java:77)
    Information:java: at com.sun.tools.javac.parser.JavaTokenizer.getLineMap(JavaTokenizer.java:763)
    Information:java: at com.sun.tools.javac.parser.Scanner.getLineMap(Scanner.java:127)
    Information:java: at com.sun.tools.javac.parser.JavacParser.parseCompilationUnit(JavacParser.java:3130)
    Information:java: at com.sun.tools.javac.main.JavaCompiler.parse(JavaCompiler.java:628)
    Information:java: at com.sun.tools.javac.main.JavaCompiler.parse(JavaCompiler.java:665)
    Information:java: at com.sun.tools.javac.main.JavaCompiler.parseFiles(JavaCompiler.java:950)
    Information:java: at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:857)
    Information:java: at com.sun.tools.javac.main.Main.compile(Main.java:523)
    Information:java: at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129)
    Information:java: at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138)
    Information:java: at org.jetbrains.jps.javac.JavacMain.compile(JavacMain.java:168)
    Information:java: at org.jetbrains.jps.incremental.java.JavaBuilder.compileJava(JavaBuilder.java:388)
    Information:java: at org.jetbrains.jps.incremental.java.JavaBuilder.compile(JavaBuilder.java:289)
    Information:java: at org.jetbrains.jps.incremental.java.JavaBuilder.doBuild(JavaBuilder.java:197)
    Information:java: at org.jetbrains.jps.incremental.java.JavaBuilder.build(JavaBuilder.java:168)
    Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.runModuleLevelBuilders(IncProjectBuilder.java:1238)
    Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.runBuildersForChunk(IncProjectBuilder.java:912)
    Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.buildTargetsChunk(IncProjectBuilder.java:984)
    Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.buildChunkIfAffected(IncProjectBuilder.java:871)
    Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.buildChunks(IncProjectBuilder.java:696)
    Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.runBuild(IncProjectBuilder.java:387)
    Information:java: at org.jetbrains.jps.incremental.IncProjectBuilder.build(IncProjectBuilder.java:194)
    Information:java: at org.jetbrains.jps.cmdline.BuildRunner.runBuild(BuildRunner.java:137)
    Information:java: at org.jetbrains.jps.cmdline.BuildSession.runBuild(BuildSession.java:294)
    Information:java: at org.jetbrains.jps.cmdline.BuildSession.run(BuildSession.java:125)
    Information:java: at org.jetbrains.jps.cmdline.BuildMain$MyMessageHandler$1.run(BuildMain.java:232)
    Information:java: at org.jetbrains.jps.service.impl.SharedThreadPoolImpl$1.run(SharedThreadPoolImpl.java:44)
    Information:java: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    Information:java: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    Information:java: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    Information:java: Errors occurred while compiling module ‘testing’
    Information:3/31/16, 4:29 PM – Compilation completed with 1 error and 0 warnings in 5m 59s 47ms
    Error:java: OutOfMemoryError: insufficient memory

    • Nikolay Chashnikov says:

      How big is your project? Probably the default heap size isn’t sufficient to build it, try increasing “Build process head size” in File | Settings | “Build, Execution, Deployment” | Compiler.

      • Jeremy Barrow says:

        I’m getting the exact same issue.
        I’ve bumped it up to 2048 MB, and testing it now, but it’s weird because Eclipse can do it with less than 900MB, so I don’t know what’s changed to make it do this.

  6. Sathish Dharma says:

    Sorry for typo. It’s OutOfMemoryError.

  7. wumin says:

    it become so slow.

  8. Tefa says:

    Still no fix for gradle mutli module support. https://youtrack.jetbrains.com/issue/IDEA-153231

    This is really a deal breaker for MANY people to use the new Idea version. Please fix

  9. Ivan says:

    Start of Typescript debugger became faster (from 2 minutes to 20 seconds)! Thank you!

  10. neuron says:

    the idea 2016 can’t compare files under mac os 10+

  11. Dmitry says:

    IntelliJ Idea 2016 was unable to apply the downloaded patch (OutOfMemory error) with thedefault heap size. I had to change it to 2048m manually to resolve it. Unfortunately I haven’t copied the log, and it was overwritten during the last (successful) update.

  12. Wayne Wang says:

    Hi~
    I’m very glad that the update is out.

    However, after update my idea to 2016, the idea consume too much CPU that I can hardly work with the new edition.

    A simple operation may cause the idea use more than 20% cpu even to full cpu. I don’t know why. What I can do is only to downgrade it to 2015.

    Hope you will fix it soon.

  13. john says:

    Did the ‘Find Usages’ functionality just changed? I can only seem to find in-module usage even though it says ‘in Project Files’..

  14. lineNumberConfused says:

    Why intellij idea 2016.1 and 2016.1.1 cannot show line number in run console?
    Right click in the editor and you can choose to click show line numbers, but the console does not offer the same choice.
    I’m sure II 2015 or earlier version did offer.
    used in mac osx 10.11.3!

  15. rexebin says:

    The new version somehow become very slow, cannot see cpu or memory pikes, but it is just slow.

    My computer is a recently purchased top spec desktop, yet I need to wait for 2 sec for the recent files to pop open the first time. When I write code in ts files, the editor is so slow that it cannot follow my typing speed which is not very fast.

    Something is wrong for sure, reversing back to 11.0.3, everything is so smooth!

  16. rexebin says:

    I deleted all my previous version of webstorm and did a clean install of the latest webstorm 2016.1.1, it seemed that the smoothness is back.

  17. David Zhao says:

    My PyCharm is consuming 100% CPU after starting – without running any codes. I thought it was due to some updates, so I left it for hours, but it’s still the case. Don’t know what is going on for using so much resources.
    The editor also gets slow, sometime got stuck when editing the code.

  18. blab says:

    Random thought:

    ‘Optional.get()’ without ‘isPresent()’ check should be weak warning for test code by default, I think.

    • Yann Cébron says:

      You can setup custom inspection severity by scopes.

      • blab says:

        Yep, I know. Just thought maybe it should be considered to be weaker for test-code by default.

        Personally I see no such cases for test-code, where I would like to avoid getting an error if the element does not exist. Unless I do and I expect it to not exist.

  19. Sebastian says:

    Unfortunately Idea is very slow after updating to this patch and I think that it is connected with some enormous disk usage. I see it on performance view of task manager on windows 7 and slowest operations are connected with changing file name or moving package from one place to another or even with creating files.
    Project is a Gradle project with Java 8.
    Maybe it is something with caching?

  20. Pete O'Bryan says:

    Immediately after upgrading from 2016.1 to 2016.1.1 the IDE began indexing a *.sql file and continued trying to index it, using enough CPU to make my laptop hot. I edited the project properties, marked as “Excluded” the “Database” directory where I keep *.sql files. That fixed the issue, but of course now I no longer have an integrated view of my sql files.

  21. Gang Chu says:

    Seems My IntelliJ got slow too.

    When I typing code, CPU stay hight usages.

    Now, I roll back to last release(2016.1), which seems released at Mar 17, 2016. And My IntelliJ smooth again when I typing code.

    PS. My ware: MacBook pro 15 (2.8GHz, 16G RAM), just purchased last month.

  22. Marshall says:

    I upgraded to Rubymine 2016.1, and WOW is it ever slow. If I click somewhere, it takes a noticeable amount of time to move the cursor. If I type text into an editor, it can take upwards of a second for it to show up. Changing the active tab is very very slow.

    It’s not busy indexing, and the used memory varies widely from ~150mb to ~500mb (out of 500mb for the JVM). If I bring the activity monitor up and start using Rubymine, the process spikes the CPU quite frequently.

    I have a newer Macbook Pro with a Core i7-4870HQ processor, 16gb RAM, and a 500gb SSD.

    As it is now, it’s unusable on my machine and I’m forced to downgrade to Rubymine 8.0.

  23. John says:

    When I tried to add a namaspace in the spring configurion xml or springMVC-config xml, I coudn’t get any code hints for the namespace. For example, in the version 15, when I wrote xmlns:context=”context”…..I can got the path of Context’ namespace. And it was the same as xsi:schemaLocation=””, I couldn’t got code completion hints as I got when I use version 15. Please fix it!

  24. Andreas Merkel says:

    This version is unusable. As soon as I start editing a file, Pycharm freezes and CPU usage jumps to 100%.

  25. Doe says:

    My Pycharm 2016.1.1 hangs with 100% CPU usage after a few minutes. I haven’t identified any triggering event – it occurs when I run familiar scripts that was working fine in 2016.1.

    • Andrey Cheptsov says:

      A CPU snapshot may help us identify the cause. We would appreciate if you could take it and send us. Here is the instruction how to do that: https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems

    • Lukas says:

      Did you try to change project to other one?

      In my case the same issue occurs on one project only. I think it’s the one I have opened when I made an update. Currently, when I start Pycharm on some other project everything is OK until I switch the project to the one on which the issue occurs. Soon after, Pycharm start to use a lot of CPU and it hangs.

      I tried to downgrade Pycharm to 2016.1 but without success. I still have excessive CPU usage although previously on this version everything was fine.

      I suppose that something went wrong during an update process and some project settings are broken which causes this issue.

  26. John says:

    (Here I can’t get any hints for completion code. I have to manually write down each key!)

    When we use “LocalSessionFactoryBean” and finish the property of “hibernateProperties”, we do can get the key from IDEA.

    ture
    true
    update
    <prop key="hibernate…….."

  27. John says:

    In this situation, I can’t get any hints for keys, I have to write them down one by one,word by word, it’s just not smart….sadly

    ture
    true
    update
    <prop key="hiber…….."

  28. John says:

    In this situation, I can’t get any hints for keys, I have to write them down one by one,word by word, it’s just not smart….sadly

    ture
    true
    update
    <prop key="hiber…….."

  29. Pascal Welsch says:

    The font looks a lot bolder than in Android Studio on OSX. And it’s a little bit blurry

  30. Hans Adler says:

    After updating today (I had to run IntelliJ as root for the first time for this, and afterwards I had to make /usr/local/bin/idea world-executable again!), IntelliJ tells me it is version 2016.1.0 and keeps asking me to update 2016.1.1. When I try to update again, it downloads and seems to install something (without messing with the rights for /usr/local/bin/idea again), and restarts. Then the same happens again, in an endless loop.

  31. Patrick says:

    Why Shift+Esc cannot let cursor go back to editor automatically?
    I need press Esc let cusor go back to editor first then using Shift+Esc hiding find window, that’s annoying.

    all previous versions are not like this.

  32. Tonni says:

    hi,

    when I tried to run a html file with bootstrap by intelliJ IDEA 2016.1.1 and it shown me like this:
    Index file doesn’t exist. 404 not found

    how can I fix that problem?

    Thanks

  33. David Spiegel says:

    Patches never work. I am running 2016.1 and attempted to install patch, but it pays no attention to my config settings and creates a new .PhpStorm2016.1 folder in my project home directory (~/Projects). My config is setup to use .PhpStorm folder in ~/Projects/apps/.PhpStorm and PhpStorm is located in ~/Projects/apps/PhpStorm2016 folder .

    So when PhpStorm restarts after patch, it does not see the patch information because IDE is not looking in ~/Projects/.PhpStorm2016.1 for config but in the defined ~/Projects/app/.PhpStorm folder I have configured. No patch files are seen.

    So I am unable to install patch. This is not first time. It occurred for any previous patches also.

  34. iShishir says:

    After upgrade to 2016.1.1 idea is very very slow. You can’t even type code. Even search results are slow.
    Env Det: running idea64.exe on Win 7 i7@2.7Ghz with 16 GB of RAM

  35. Waqar Arshad says:

    Is there any solution for the Slowness of IntelliJ 2016.

  36. Kostas says:

    Hi, you used to have a zip download format in previous releases but the URL doesn’t work anymore (https://download.jetbrains.com/idea/ideaIU-2016.1.2b.zip). In my corporate network we are not allowed to download executables. Is it possible to make the windows zip file available again?

    Cheers

  37. Poul says:

    Could you provide any links to previous versions without patch for other platforms ? Entire teams can not work because of your latest update. Could you provide any workaround? When it will be fixed ?

  38. Haojun says:

    Recently I realize that if I’m opening two projects with two separate Intellij windows, it is very slow and sometime it’s even freezing.

Leave a Reply

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