Since last update to version 2021.2, PyCharm eats a lot of memory
Hi there,
Here is my configuration:
PyCharm 2021.2 (Professional Edition)
Build #PY-212.4746.96, built on July 27, 2021
Licensed to Multiply Software Limited / Jean-Hugues de Raigniac
Subscription is active until April 4, 2022.
Runtime version: 11.0.11+9-b1504.13 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 5.4.0-80-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 6110M
Cores: 4
Registry: debugger.watches.in.variables=false
Non-Bundled Plugins: AceJump (3.8.3), GrepConsole (11.10.211.6086.0), Key Promoter X (2021.2), Statistic (4.1.7), com.firsttimeinforever.intellij.pdf.viewer.intellij-pdf-viewer (0.11.1), com.intellij.javafx (1.0.3), String Manipulation (8.15.203.000.3), indent-rainbow.indent-rainbow (1.6.1), org.sonarlint.idea (5.2.0.35150), org.jetbrains.plugins.vue (212.4746.57), sourcery.pycharm-plugin (0.9.3), izhangzhihao.rainbow.brackets (6.19)
Current Desktop: ubuntu:GNOME
I added 2Go of RAM to its runtime to no avail, its eating as much memory as possible and I have to stop and restart the IDE to free memory.
Please sign in to leave a comment.
May I ask you to capture the Memory snapshot following the article https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems, then file a ticket to https://youtrack.jetbrains.com/issues/PY and attach the snapshot along with the logs folder zipped from Help | Collect Logs and Diagnostic Data?
If the file is too big to be attached to the ticket, upload it to our FTP server https://uploads.services.jetbrains.com/ and let me know the upload ID.
It will help us investigate the issue.
Thank you for this suggestion but because of NDA's restrictions I can't send you logs containing code information.
I found a ticket related to this issue: https://youtrack.jetbrains.com/issue/IDEA-264677
Meanwhile, is there a way for me to send you manually obfuscated logs and still have JetBrains analyse it?
Sure, you can manually edit them to remove all the sensitive information. It shouldn't get in the way of troubleshooting.
Editing a Memory snapshot won't be possible I'm afraid.
Thank you.
Your reference to the memory snapshot made me think I could have a look at it.
That was useful since it revealed SonarLint plugin is using a lot of memory. Disabling it fixed the problem.