IntelliJ IDEA 2018.3.4 is released!

Today we are ready to release the fourth bug-fix update for IntelliJ IDEA version 2018.3. With IntelliJ IDEA 2018.3.4 we’ve fixed a number of regressions and bugs. Here is a list of the most notable ones:

  • Fixed the Java code analysis so it does not get stuck with the equals method when huge numbers of fields are compared using Objects.equals() : IDEA-204984.
  • Fixed the IDE freezes on the “Save Test Results” action while running the JUnit tests: IDEA-205448.
  • Fixed a regression so now the Code Generation settings are saved correctly: IDEA-204185.
  • Fixed the regression that caused the “Attach Gradle project” file chooser to filter out .gradle.kts files: IDEA-193640.
  • Fixed the regression that caused the loss of the Gitlab Token in the task server settings, after closing the IDE: IDEA-205214.
  • Fixed a regression so the IDE now correctly recognizes scratch files: IDEA-204857.
  • Accessibility improvements: IDEA-204449, IDEA-203712.

You can find the full list of addressed issues in the release notes. If you’ll encounter any issues, please don’t forget to submit them to our issue tracker.

Happy developing!

About Zlata Kalyuzhnaya

IntelliJ IDEA Marketing Manager at JetBrains. twitter: @ZlataKalyuzhnay ‏
This entry was posted in EAP Releases and tagged , , , . Bookmark the permalink.

13 Responses to IntelliJ IDEA 2018.3.4 is released!

  1. Gary Halcon says:

    “Scanning files to index” is still an issue and makes the IDE unusable.

    -Linux

    • Maksim Mosienko says:

      Please share your problem in more detailed way in YouTrack and we’ll try to help.

    • nullsteph says:

      On a low powered laptop it is. Let me recommend getting 32GB ram with a k series cpu in a System76 laptop. Indexing will be quick. You can be mobile friendly or develop pain free but not both.

      • Matt J. says:

        Microsoft can index an entire drive reasonably quickly even on a ‘low powered laptop’. Why is IntelliJ having trouble indexing a smaller number of files? On the surface, it appears that Microsoft is using the right algorithms implemented efficiently while IntelliJ is using a virtual memory implementation of Bubble sort:(

        Now as I just admitted, this is only the surface appearance. But the point is it is suspicious that Microsoft can do the indexing in a reasonable time and IntelliJ cannot solve what looks like a simpler indexing problem.

  2. Tamas Herman says:

    @Gary, which YouTrack issue is that “Scanning files to index”?

    It’s a very costly operation usually and I saw a lot of people are trying to use JetBrains products on medium range machines, where indexing takes annoyingly long, like 2014 i5 MacBooks with “only” 8GB RAM.

    I agree, it’s pretty sad you need more than that to make the experience bearable, but it’s a one-off cost to invest into some 4, 6 or 8 core i7 or i9 machine with significantly larger L3 caches than the i5s and pump your memory up to 16GB or 32GB RAM, so you can have plenty of browser windows open alongside the IDE, which would take up, let’s say 4GB RAM.

    However, the benefits you get from the IDE understanding the concept of a project and the structure of the source code greatly offsets that annoyance and still significantly amplifies your intellect a lot quicker than most of us can achieve with other forms of self-improvement.

    As a side note, if you are working with Node.js projects, then switching from npm to yarn or https://pnpm.js.org/ greatly reduces the number of unique files the IDE is going to index, hence drastically reducing indexing times.

  3. Nail Samatov says:

    Java scratches are unusable on big projects because of IDEA-185342. Is there a chance that you fix it soon?

  4. Daniiel says:

    I am trying to use the “pnpm” and there is no success.
    Any tutorial how to do it ?

    Thanks

Leave a Reply to Onlinetop Cancel reply

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