PhpStorm 2022.2.1 and CPU usage
Hi,
The new update seems to fix the freezing problem, however I'm concerned by the CPU usage which is constantly high, and the IDE doesn't look to be doing anything
There is no indexing operation in progress or anything else in background so I don't understand.
I've provided logs here : https://intellij-support.jetbrains.com/hc/en-us/requests/4237613
Edit: the CPU usage suddenly dropped to 0 but still I wonder why it was happening
Kind regards
请先登录再写评论。
Ali4322abbas , any chance PhpStorm is indexing when you experience the issue? Please refer to this screencast.
If not, please check how it goes after File | Invalidate Caches | Invalidate and Restart.
If the same, please capture a CPU performance snapshot about a minute long while there's a high CPU load and share it together with the logs (Help | Collect Logs and Diagnostic Data) in a support ticket (Help | Contact Support).
Thank you!
I'm having the same issue after a recent update, MacOS activity monitor reports 900%. The entire system becomes unusable even when indexing concludes (Which seems to start from scratch every time I open PhpStorm)
Basically, the indexing operation could significantly load CPU but it should not happen too often. I would suggest to collect log files (Help > Collect Logs) and submit a support ticket or a YouTrack report:
https://youtrack.jetbrains.com/newIssue
Also, as mentioned above, CPU snapshot (when no indexing is running) could be quite useful.
You may find more information on how to collect performance data here:
https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems
PhpStorm 2023.3.2
Build #PS-233.13135.108, built on December 21, 2023
Linux 5.15.0-91-generic
Memory: 8192M
Cores: 12
The CPU usage:
My request to support team was completely useless. After couple days of discussing they are ignoring me.
As soon as I start typing, the cpu usage goes up a lot.
CPU usage snapshot ID: 2024_03_08_2BxdXcgizZBbauQzZwoWhb
Hello!
Could you help me, what's going on?
It happens really often
Easiest way to fix this is to switch to M-based mac