I am seeing something similar. I have the previous version (1.2.0?) and everything was working fine. I upgraded to Firebug 1.2.1, and now stepping through code after a breakpoint is very slow. Sometimes so slow that after a few seconds, a dialog pops up and tells me the script is not responding, and gives me the option to continue or cancel debugging.
What happened to the debugger? On Sep 12, 6:52 am, Jafar <[EMAIL PROTECTED]> wrote: > Hey, all -- > > I'm wondering if anyone else is seeing this behavior. If I set a > breakpoint in my code or set "Break on all Errors", especially on Mac > OS, with Firefox 3 + Firebug 1.2, when it stops at the breakpoint, the > mouse cursor turns into a watch and the whole UI of Firefox becomes > frozen. I have to force quit the browser. > > In Linux, I'm seeing a similar behavior, but it's not quite the same. > I can still click around in the browser, but the debugging UI is > frozen. > > Using Firefox 2 works perfectly. I haven't tested this on Windows. > > I seem to recall that this was an issue for me in most betas of > Firebug 1.2, but I thought it was fixed in later ones. Now, > inexplicably, it's back. > > Is anyone else seeing this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
