Page won't load with debug "on" but with IDE not started about xdebug-helper-for-chrome HOT 9 CLOSED

Hi! Thanks for using XDebug helper and reporting this issue. It sounds like an issue with XDebug itself and not so much with this extension. Could be that you trigger the "XDEBUG_SESSION_STOP_NO_EXEC" setting or so, that would explain the script not executing.

Could this or another XDebug setting be the cause of this? Maybe you could share your settings/how you've used XDebug in the past to investigate this further.

from xdebug-helper-for-chrome.

Hi,

This are the contents in my config;

[XDebug]
xdebug.remote_enable=true
xdebug.remote_port=9200
xdebug.remote_connect_back=1
xdebug.profiler_enable_trigger=1
xdebug.profiler_output_dir=/tmp

As far as I know this shouldn't cause any problems. I used an other debug tool before XDebug so I can't tell how I used it in the past.

from xdebug-helper-for-chrome.

Thanks for posting this, I'll take a look. What was the other tool you used before?

from xdebug-helper-for-chrome.

I used the "PHP DBG Debugger" with NuSphere PHP ED
(http://www.nusphere.com/products/dbg_wizard_download.htm)

from xdebug-helper-for-chrome.

Okay, I've done a bit of research and found this issue on the Xdebug Mantis. Looks like your issue, but sadly I can't reproduce it myself.

With the Mantis issue in mind I would ask you to test 2 things:

1. If you telnet to 127.0.0.1 on the xdebug.remote_port (9200 in your case) does it refuse the connection immediately? On my machine it does, but if it doesn't on yours this could make Xdebug wait for the refuse/timeout.

2. If you enable Xdebug by hand (not using the Chrome extension) by adding a GET parameter or a cookie by hand, does the script still hang if no debugger is listening? This would tell us if it's Xdebug itself that going wrong or the extension that is setting some cookies the wrong way.

Hope you can take a look at this!

from xdebug-helper-for-chrome.

Hi,

Thank you for your effort so far!

Question 1:

From a client to the webserver
9000: about 30 seconds till it closes
9200: about 2 seconds till it closes

From the webserver to 127.0.0.1
9000:
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.
(this happens within a few seconds)
9200: refuses imidiatley

9000: port is used by an other process
9200: port used by Xdebug

Just to be sure: I'm NOT developing on the same server as where the webserver is running.

Question 2:

The script will still hang, so that confirms that there is no problem with the browser plugin.

Thanks for your help!

from xdebug-helper-for-chrome.

Looks like it's related to the Xdebug issue I referred earlier about: http://bugs.xdebug.org/view.php?id=963

I'm going to close this, would you mind to report this issue in the Xdebug developers Mantis? Hope they can take a look at it for you. I also pinged them about this issue here on Github, so I hope they can take a look at this and solve it for all of us. :)

Don't hesitate to comment if you need to know or want to report something about this!

from xdebug-helper-for-chrome.

Hi,

Thanks! I created an account on the bugtracker but I cannot comment on the issue. I don't know if you can add me so I can comment on it?

from xdebug-helper-for-chrome.

I'm sorry, but I can't. I've no special rights on that bugtracker, maybe you could open a new issue?

from xdebug-helper-for-chrome.