When using PhpED with DBG I have Firefox as default browser. When NOT using PhpED I also have Firefox as default browser.
Numerous times I have experienced that when I start up a site from within Firefox I get a message similar to the following:
----------------------------------------
DBG 3.1.6
Failed to run DBG session
Reason: failed to connect to the client address xxx.xxx.xxx.xxx.xxx
Not sure what it means? Visit http://www.nusphere.com/dbg/ for troubleshooting.
Debugger request: "396988202880300001;d=1,p=0,c=1"
Request found in: "$_COOKIE['DBGSESSID']"
Target PHP version: "5.1.4"
Server API: "CGI/FastCGI"
Extensions API: "220051025"
Modules API: "20050922"
PHP API: "20041225"
----------------------------------------
The client address is, of course, something that relates to "localhost".

The problem is that DBG in some way or another leaves my default browser in a state of disarray that is unacceptable.

Even when I type, by hand, the address from which I want to see the home page (i.e. something like "http://localhost/MySite" and MySite was the last site I used PhpED/DBG on) and even after resetting my computer several times, the same message keeps coming up.
And yes: the last session of PhpED WAS closed the proper way, allowing it all the time it needed to close down properly (which, I may assume, includes everything required to shut down DBG properly).
NOTE: Opera nor IE, Safari (Windows) or even 'Chrome' experience the same problem at that same moment!. They all show that homepage as expected.

Conclusion: "there's something rotten in the state of DBG".

What to do about it??

Does this happen if you clear the cookies (for trouble shooting) Thanks!

[quote="yfaktor"]Does this happen if you clear the cookies (for trouble shooting) Thanks![/quote]

After several more resets and clearing [b]session cookies[/b] (through the developper toolbar), things seem to be normal again.

Now I may have misunderstood this for all my life but as far as I know [b]session cookies[/b] should be cleared when a session ends. Let alone that they could survive a system reset. Obviously PhpEd/DBG are playing tricks here