Firebug with error message "Debugger is already active" after update 1.6.0?

Question

After the last update of Firebug 1.6.0, I continue to receive this error message while debugging (on the "Script" tab):

The debugger is already active.

The debugger is currently stopped at a breakpoint on another page. Go to this page

Good, but "Go to this page" doesn't bring me anywhere, and I can't debug anything. I have only one instance of Firefox working, restarting it does not help ... even uninstalling the add-in and reinstalling it does nothing. Is there a way to remove breakpoints from the command line, what happens here?

Edit: Going back to 1.5.x, solves the problems, but even going up to 1.7.x alpha, reproduces the problem, I would report an error, but if I'm the only one who survived it, t most of the error.

Answer 1

We believe this problem has been fixed for Firebug 1.6.1; 1.6.1b1 can be found at http://getfirebug.com/releases/firebug

I would love to hear more error messages on this particular issue. This is probably an extension conflict, so we need people to publish the result of the url "about: support" so that we can compare the lists or we need you to try installing Firebug in a new Firefox profile and then add the extensions until you find the problem. (I doubt jQuery is involved, or we will catch it in beta testing).

See also http://code.google.com/p/fbug/issues/detail?id=3724 http://code.google.com/p/fbug/issues/detail?id=3719

Jjb

Answer 2

My workaround: go to the profile directory and delete firebug / breakpoints.json.

Firebug 1.6.1 on Firefox 3.6.13 on MacOS 10.6. Tried to disable all other extensions and no luck.

Answer 3

Very suspicious. Espionage is what I get. Other suspicious messages Firebug Script.

> No Javascript on this page > > If <script> tags have a "type" attribute, it should equal > "text/javascript" or "application/javascript". Also scripts must be > parsable (syntactically correct). > System sources can't be debugged > > Firebug currently can't be used to debug user agent internal files. > See issue 5110 for the reason. You may use the DevTools Browser > Toolbox instead.