First let's consider that Firebug is used by tens or hundreds of thousands of people every day. Then let's read your post. It seems to me that a better title for the post would be "Mavi Gozler has a Nightmare" ;-)
The three most common causes of these "Firebug Nightmares" are 1) Extension conflicts: some other extension which works fine interferes with Firebug's operation, 2) Some data in the Firefox profile that breaks Firefox in a way that is only seen when Firebug operates, 3) An unusual set of options or pages that Firebug developers have never seen. We can eliminate the first two as a cause if you install Firebug in a new Firefox extension and repeat your testcase. http://kb.mozillazine.org/Profile_Manager#Creating_a_new_profile On Nov 20, 11:51 pm, Mavi Gozler <[EMAIL PROTECTED]> wrote: > Firefox 3.0.4 with Firebug 1.2.1 > > 1. When a reload of a page is done, the loading hangs. My guess is > that this is related to Firebug being in the middle of a debug > session. It does not seem to occur when Firebuy is NOT in the middle > of a debug session--that is, when the Continue funciton is used to get > Firebug out of a script. Firebug does not have a Continue function. > > 2. If a page is reloaded with a script, its script will stop working, > even though the script is bug-free. This is probably related to the > related to Firebug being in the middle of a session on another page. This paragraph makes no sense. "its script" means which script? What mechanism would cause Firebug to suddenly decide to sabotage a script in a page? What does it mean for Firebug to be "in the middle of a session"? > > 3. The suspension and resumption of Firebug does not seem to work at > all. A breakpoint that is set won't be caught. This is true when > Firefox is even re-started. Suspension and resumption of Firebug has nothing to do with breakpoints. > > 4. In clicking on the pages of these discussion groups, Firebug came > up and I disabled it for use on this site. I then clicked the next > page for discussion, and loading was hanging. When reloaded the > intial page and then clicked next page, it still hung. When I clicked > away the tab and re-opened a new tab, the loading of the next page > still hung, despite Firebug having been disabled. Firebug probably sensed that you were going to post something unpleasant to the newsgroup and tried to prevent it. > > 5. In closing down Firefox, I am unable to restart it. This is > because Firefox continues as an invisible, high CPU-using (50%) > process that must be ended from within the Task Manager. Every time I have looked into this kind of problem, the cause has been an error message raised within the error handling code that triggers on exit, causing errors, which trigger the error handling code, ... The looping behavior is a Firefox bug. The best we can do is try to protect against error propagation within Firebug's error handler. > > 6. All these problems seem to go away when Firebug is disabled. This however does not mean that Firebug is the cause. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
