This time, both browser and eclipse are stuck, and Eclipse freezes at “Launching [project]” 57% (in this case), with details saying “Launching: waiting for XDebug session”.
Looks like a different problem, but for a moment I thought that solution was the same as here.
I apologize to those who have already been there and failed to solve the problem.
As can be found elsewhere, the problem is in the port. XDebug on machine running Eclipse is actually a server listening (by default) on port 9000, fed with debug data thru apache xdebug module.
In my case, particularly frustrating was the fact that debugging in Eclipse was working, and after not using it for a while it just stopped.
In my case, the solution was cleanup of unnecessary software. It turned out that some of it had occupied the port 9000, so XDebug was again able complete the full cycle of exchanging data.
So, as there is no general answer to the question what is already on the port 9000, I can suggest another solution: find one of the free ports (start searching from 9001, 9002, etc.) on machine running eclipse. Make sure you don’t forget to change configuration in both eclipse and apache xdebug module.