Intellij IDEA Ultimate 2020.3 memory leak issue.

Sorry for the inconvenience.

This report is not useful without the memory snapshot: https://intellij-support.jetbrains.com/hc/en-us/articles/207241235.

I cannot send memory snapshot, unfortunately.

happens to me too all the time.

Ever since upgrading, I'm having this issue as well. It's a relatively slow leak, but 4GB+ with 4 small files open? Ridiculous. It wasn't this way with 2020.2.4.

Hi,

If anyone who experiences this memory leak issue could help share a memory snapshot, please refer to https://intellij-support.jetbrains.com/hc/en-us/articles/207241235 (Memory Leak or High Memory Consumption section) and share us with a snapshot.
After capturing, you could open a bug report here https://youtrack.jetbrains.com/issues/IDEA with the snapshot, and changing to "Visible to" to jetbrains-team.

If no one can't share it, please try to provide the steps or open which file types can reproduce this memory leak. You could right-click the IDE status bar and select Memory Indicator to enable an indicator to monitor it.

Same here.

Most obvious when editing an OpenAPI 3.0 YAML file, with or without Preview pane open. CMS Old Gen sweeps have diminishing returns, touches the major GC threshold with almost no harvest from the major GC sweep, goes flat for a while (until the Par New pools fill up I guess) and then just keeps growing until it starts succumbing to the more and more frequent GC sweeps.

Cycling (closing/reopening) the project helps a few times until it no longer does. Then a restart is required.

Reopening the file, the cycle restarts the moment I start editing the file. If I stop typing, the growth pauses after a while but memory use has increased by an amount disproportionate to the amount of typing. Half of that memory is recovered by pressing the Perform GC button in jconsole.

If it's not the OpenAPI plugin per se, it might be the spellchecker, code completion or some other caching or change event generation. However, it does not appear to be a problem when editing f.i. Groovy files. And running a batch of functional tests (613) on the Groovy Grails project has an expected effect on memory pool behaviour with memory use falling back almost to pretest level.

If I find the time later this week I will do some tests on a toy project. The memory snapshots contain security-sensitive info and IP.

@Guy Bormann Could you please try the IDEA 2020.3.1 RC from here to see if it helps: https://confluence.jetbrains.com/display/IDEADEV/IDEA+2020.3+latest+builds

We have fixed some OpenAPI plugin related performance issue in the IDEA 2020.3.1.

See some discussion about a similar issue here for details: https://youtrack.jetbrains.com/issue/IDEA-257916

Lejia Chen Ok, installing RC as we 'speak.' I will report back on the relevant issue ticket(s) if still open.

By the way, I recognise the behaviour as reported in the other tickets but did not report it here because it was obvious to me that the selection issue was related to the performance implications of the memory pressure.

Thanks for the follow-up!

Mmm, would have been nice if the Toolbox pulled the 2020.3.1 RC for Ultimate. The Community Edition is useless for my project.

Ok, back to manual download :-/

Edit: In the meantime it has become available through Toolbox.
The RC seems to have solved the issue. Memory creeps up much slower now and a push on the 'Perform GC' in jconsole makes CMS Old Gen drop to about base level (will also comment this on the ticket).

Edit bis: Oops, probably not the RC but the actual release version (Build #IU-203.6682.168).

Memory use report.

Submitted as 6081878.

I submitted the following issue: https://youtrack.jetbrains.com/issue/IDEA-259739

Downgrading to 2020.2.4 fixed the memory issue for me.

@Cviniciusm Thanks for the report. I have replied to you in that issue link. It looks the bundled "Grazie" plugin uses a lot of memory. Please try to disable the Grazie plugin in `File | Settings | Plugin | Installed tab` and restart the IDE to see if it helps.

It solved the issue.

Thanks.

Thanks, Lejia!

Together with the memory leak patch to the OpenAPI plugin in 2020.3.1, switching off the Grazie plugin significantly reduced the memory footprint.

However, I suspect Grazie is not just using memory liberally but probably has a memory leak as well.

@Guy Bormann We have fixed a Grazie plugin memory leak issue in the IDEA 2020.3.2: https://youtrack.jetbrains.com/issue/IDEA-258695
Please try that version later with the Grazie plugin enabled.

Hello everyone!.

I have the same problem since I updated to version 2020.3. PhpStorm uses so much ram memory that it easily uses 2GB of swap memory, making my system unstable. I have 12 GB of RAM / 8 Gb of Swap.

The problem occurs shortly after I execute it, when it builds the index and checks for Composer dependency updates.

My projects are Symfony 2.4 and my OS is Ubuntu 20.04 (kernel 5.4.0-65-generic, 64bits)

Hi Gonzalogcosta,

Please try using the 2021.1 EAP version from https://www.jetbrains.com/phpstorm/nextversion.

If the problem remains please raise a new issue at https://youtrack.jetbrains.com/issues/IDEA, and capture a memory snapshot as per https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems.

Thanks.

Hi Egor Klepikov

Perfect, I didn't know that version. Then I will do the installation to test it.
Thanks a lot! ;)

@Gonzalogcosta did it resolve the memory issue?

Tomerbd1 sorry for my late reply.
The update improved performance overall, but my problem is when PhpStorm updates composer dependencies in background. So as a quick solution, I opted to disable that check from the Preferences.