2019.1 Hanging on massive repo branch change Follow
PHP version 2018.3 was working just fine but after upgrading to 2019.1 every time I change branch on GIT PHPStorm gets really slow while indexing and eventually becomes unresponsive
Please sign in to leave a comment.
I found a similar problem but with 2019.1.1 preview version. Processor usage reaches 99% for quite a lot of time during branch changing.
Memory usage rise also a lot. I used to work with 2 opened projects and I've almost never exceeded the memory heap above 1GB at the start. Right now there is always ca. 1,5GB.
Did you notice anything similar once the project is just opened? Would it be possible to try disabling "Mark branches that have incoming/outgoing commits in Branches popup" checkbox in "Version Control > Git" menu window?
For me it wasn't that. I changed the refresh value for 1 minute and nothing changes. CPU was fine. I think it's probably due to inspections. Take a look at screenshot. The only one thing I have made is to press Enter in some php classes files. There are ca. 1000 lines. After each pressing the enter button, CPU rise for 5 seconds to 100% or almost.
EDIT: I can also confirm that changing branch with indexing involved after that is also causing high processor usage for X seconds. The time depends of that how long is indexing process running. Changing branch without indexing after that is very fast.
For me, it happens when switching branches only. It starts indexing takes ages and the project explorer won't even expand. CPU goes all the way to 400% sometimes and I feel like my mac is about to lift off. If I completely close the application, wait for about 10s, and open it again it goes back to normal.
CPU going up even after "Mark branches that have incoming/outgoing commits in Branches popup" is disabled
And here it is over 450%
What type of a project is that? PHP or JS? It makes sense to reproduce the issue, collect the logs bundle (Help | Compress Logs) and attach it to a support ticket: https://intellij-support.jetbrains.com/hc/en-us/requests/new?ticket_form_id=66731
In my case it's PHP project. However I checked the PHP and JS files. In both there were problems with high CPU usage caused by inspections. So basically there are 2 problems: indexing and inspections. I have already created a ticket as you asked.