The only thing that I've seen where Firefox burns CPU for a couple of minutes every so often is very obscure: https://bugzilla.mozilla.org/show_bug.cgi?id=499568 I would not have expected this to depend upon Firebug being enabled.
Another possibility is http://code.google.com/p/fbug/issues/detail?id=1948 because background ajax can fail, resulting a bunch of error messages. Hard to get 1 minute of CPU out of that however. I suggest you install the tracing version, open the tracing console, and set ERRORS option. When you see the effect, look for something in the log. More hints: http://groups.google.com/group/firebug/web/faq-about-firebug jjb On Jul 14, 10:59 am, DJWortham <[email protected]> wrote: > Same issue for me -- completely unusable for 1-2 minutes at a time > several times an hour. > I'm on FF3.5 with FB1.4.0b7 on Mac OS X (10.5.7 -- the most recent > version). > Issue started yesterday (after I upgraded to 1.4.0b7). > > Disabling Firebug resolves the slowdown. > Disabling all other FF addons (including Google PageSpeed -- which > piggybacks on FireBug) does not. > > I have Console & Net capture enabled for the site I develop for. > Multiple tabs for the same site (all of which have FireBug). Wasn't > an issue until yesterday. > > Thanks for looking into this, > DJ > > On Jul 13, 9:55 am, enigment <[email protected]> wrote: > > > No errors. I have Show Javascript, XML, and External Errors enabled. > > > - e > > > On Jul 13, 12:51 pm, johnjbarton <[email protected]> wrote: > > > > The only thing that comes to mind is tons of error messages. Do you > > > see a lot of them? > > > jjb > > > > On Jul 13, 9:34 am, enigment <[email protected]> wrote: > > > > > First, I happened to see a forum ms that b8 was out, even though > > > > Firefox Update didn't find it, so I downloaded that and let firefox > > > > restart. After that, my 25 seconds went down to about 13; don't know > > > > if it's the restart or b8. > > > > > When Console and Script both disabled, it's pretty much as fast as > > > > with firebug off. > > > > > With only Script enabled, it's maybe a little slower than w/o firebug, > > > > but not much. > > > > > Turning Console back on, back up to 13 seconds. > > > > > -e > > > > > On Jul 13, 12:23 pm, johnjbarton <[email protected]> wrote: > > > > > > What happens with Script panel disabled? > > > > > With Script and Console disabled? > > > > > > jjb > > > > > > On Jul 13, 9:01 am, enigment <[email protected]> wrote: > > > > > > > With ff 35 and every firebug beta I've tried (most of them, > > > > > > currently > > > > > > 1.4.0b7), a moderately complex modal dlg that takes a couple of > > > > > > seconds to load with firebug off takes 25 seconds to open with > > > > > > firebug > > > > > > open. You read that right, twenty-five seconds. There's always been > > > > > > some penalty for having firebug open, but this is pretty extreme. > > > > > > > That's with all tabs enabled except Net. I don't have Strict > > > > > > Warnings > > > > > > checked on the Console tab. Are there any other firebug settings > > > > > > that > > > > > > might be affecting performance to this degree? > > > > > > > Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
