Phpstorm debug hanging how to#

This topic was modified 1 week, 2 days ago by nilsnolde. But even only giving a mapping for a deeper subfolder results in the same behavior. I tried with xdebug.start_with_request=no, but then breakpoints wouldn’t trigger at all, also not mine.Īlso, in PHPStorm I didn’t need to configure much, I added the path mappings to the WordPress root inside the container.

My xdebug.ini: zend_extension='/opt/bitnami/php/lib/php/extensions/xdebug.so' My own breakpoint do work, it’s just a terrible UX that “random” code points trigger debug breaks. Obviously none of those have breakpoints set. There are many advantages to this, but first, let’s talk about the traditional way to debug hangs.

Phpstorm debug hanging how to#

We’ll see how to use a performance profiler like dotTrace to find the root cause of the hang and fix it. Whenever I interact with the homepage it triggers on every *.php file, including admin-ajax.php. In this article, we’ll see one of the best methodologies for debugging hangs. Even when the WordPress container is starting up, execution pauses, the debugger is triggered on wc-cli.phar (it’s a bitname/wordpress image, it does a lot when starting up) and I have to manually continue the program multiple times before it’s loaded. This means its out of the GoLand teams scope, and developers from another JetBrains team will take over.

I set up PHPStorm properly, actually everything is working. PhpStorm 2023.1 is now available This release is a major update that includes integration with, improved performance, enhancements to the new UI, a DFA debugger for PHP, and much more. I’m using PHPStorm 2022.3 and set up a WordPress & mariadb each in a docker container, with XDebug v3.3.0 and PHP 8.2.13 installed.