This is a bit specific situation, I am wondering if anyone else has met the following:
Chrome starts to stop when setting the xdebug session cookie. The cookie can be left after the previous debugging, all requests (ajax or "normal") are slowed down (from 15 seconds to 2 minutes before receiving) when debugging is not used. I use PHPStorm for debugging, but it doesn't matter if phpstorm works or not when a stall occurs.
EDIT: steps to play a stop:
- Open a php storm project and start debugging (index.php in my case)
- Set some breakpoints and refresh the page in chrome.
- Starting breakpoints to completion
- Click "stop debugging" on php storm
- Refresh the page in chrome (and this is the start of the launch)
Once the stop starts, the Chrome tab will become a little unresponsive, but it may be closed.
Removing the XDEBUG_SESSION cookie manually (between steps 4 and 5) fixes the problem, but I really like the working solution. One of the solutions can be switched to other browsers, since I did not experience such a slowdown on IE or FF, but I really like working with chrome.
EDIT: I also managed to create a bookmarklet that deletes the cookie, but even this solution does not satisfy me in this situation, since I have to remember to click the bookmarklet before trying to move on, otherwise the chrome will stop again.
The biggest annoyance is that I do not understand where the dump occurs, on the chrome (client) side or on the server side. I suspect chrome as this does not happen with other browsers.
I am posting a reward for this, I want to know if there is something related to XDEBUG in chrome, and if either side (xdebug or chrome / chromium) can do something with this error.
The bounty on this issue has ended, and there are no answers to award her.