PhpStorm freezes when trying to acces the PHP -> Servers settings
When I try to access the PHP → Servers settings, the entire IDE freezes and I'm forced to kill the process and restart. Unfortunately, since this is the last settings page I accessed, the IDE now freezes whenever I open the settings dialog.
I've uploaded my threaddump files here in the hopes that they will help:
Upload id: 2024_04_22_tdjS8b15LHmMdwUKWr7HX1
Please sign in to leave a comment.
Hey,
Thank you for sharing the freeze thread dumps.
Would it be possible to collect & share a full logs pack?
(Help > Collect Logs)
Hi here's my logs:
Upload id: 2024_04_23_6YpLJi7fKonFpZr7KtETdG
Thank you for sharing the full logs pack.
Basically, there is a similar issue on YouTrack:
https://youtrack.jetbrains.com/issue/WI-77238/PhpStorm-stuck-when-trying-to-create-a-new-Server
Both your case and the one mentioned above also have signs of the following issue:
https://youtrack.jetbrains.com/issue/WI-76242/UI-freezes-in-com.jetbrains.php.composer.lib.ComposerLibrariesNodePatcher.
So it might be related to the Composer subsystem or, to be specific, a structure/number of added packages.
Could you please tell a bit more about your project?
Do you have multiple composer.json files in it? Can you share a project's `.idea` folder as well?
Interesting…
I'm not using the AWS plugin. So the first issue you linked isn't really relevant.
However, the project is a drupal project with multiple contrib drupal modules which typically have composer.json files in them. So it's possible the second issue is related.
Here is my .idea folder (gzipped): Upload id: 2024_04_23_22e9ANTWmX9GbQRdwNeww8
Thank you for sharing the `.idea` folder!
Turns out it has nothing to do with the AWS plugin, it was just a theory.
Apparently, it is an aforementioned Composer issue causing this new problem. Personally, I have seen it on Magento and Drupal projects with lots of dependencies and child “composer.json” files.
We will try to reproduce it on our side and deliver a fix as soon as possible. Thanks again!
Just sharing that…
Mine has been frozen a couple of times on randomly different Magento 2 projects, upon clicking to PHP > Servers, regardless of the weight.
As a workaround, I first removed .idea folder so the IDE might start all over again and hopefully it worked.
Recently, I simply removed the path to composer.json and it's also resolved.
Looking forward for a fix soon.
Thanks.
the same happens for me with few Magento 2 websites
removing .idea directory helps
I have the same problem when upgrading to 2024.2 for all my magento installations. Basically freezes on the Php→Servers window.
Removing project's .idea helps but of course I lose all my settings for the project (xdebug, exlude and source folders ecc). Not really a viable solution but can be used as a last resort.
it seems something has changed on the way 2024.2 reads the xml files in .idea that contains the “Servers” list.
As a better workaround rename the .idea/workspace.xml file and it will work just fine. After a few tests it turned out it is the workspace.xml component composerConfigs:
there are no more that 70 lines in the file ComposerConfigs component.
this seems to confirm Vasiliy Yur theory about the issue being related to child composer files, but perhaps it's more complicated than that. I thought I could easily reproduce with a vanilla magento 2 installation. But the thing is this: let's say I have 10 different magento 2 projects: when you experience the issue with project “1" you can close project 1 and go to project “2”, “3” ecc and they all experience the issue as log as you have something already set in Php→Servers. But when you fix the .idea in the project "1" folder…. the other projects get fixed as well, no matter if they have their own .idea folder. This is absolutely weird for me and I can not find any explanation for that. Perhaps it has something to do with a global reindex being carried out after upgrade? this will lock many functions but if it is the case, the notice reindex in progress does not appear: it could simply be “under the hood” as a consequence of the 2024.2 upgrade.
**********
Furthermore, if submitting a report for an error it gives “Success” and then a successive popup with “Error” pops up and it is not possible to close the “Report error” popup window: it continues to popup in a loop. The only solution is killing phpstorm via terminal.
Running 2024.2 on Ubuntu 20.04.6 LTS