I've seen something similar to this where the entire console stops working (logging, XmlHttpRequests, etc). All the other panels appear to be working correctly. I've opened a bug report http://code.google.com/p/fbug/issues/detail?id=2948 and have attached the tracing output. As mentioned in the bug, refreshing the page doesn't fix anything. Restarting Firefox does.
Trevan -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Honza (Jan Odvarko) Sent: Thursday, March 18, 2010 9:01 AM To: Firebug Subject: Re: Console stops outputting XmlHttpRequests after a while...bug? I haven't seen any report about this yet, but what you can do to gather more information about the problem is installing 'X' Firebug build and see possible error logs in Firebug's tracing console. 1) Get http://getfirebug.com/releases/firebug/1.5X/firebug-1.5X.3.xpi 2) Open Firebug Tracing Console (Firebug -> Open Firebug Tracing) 3) Check ERRORS and SPY options in the console 4) Use Firebug as usual and watch the console. * 'SPY' logs are related to the 'Show XMLHttpRequest' feature. Having the console on, can represent a performance penalty (due to the logging). Honza On Mar 18, 1:36 pm, OnDistantShores <[email protected]> wrote: > Hi, > > I recently upgraded to Firefox 3.6 and Firebug 1.5.3 at about the same > time. > > Since then, I get a strange, annoying, intermittent bug with Firebug's > console tab. I have it configured so that Javascript errors and > XmlHttpRequests show in the console. > > It seems that after a little while (or after a Javascript error comes > up? I'm not entirely sure), XmlHttpRequests stop printing out to the > console. Javascript errors still show up, but it takes a reboot of > Firefox to get XmlHttpRequests coming through again. If it was a > timeframe, I'd have to guesstimate every 30 minutes or so. I use it > constantly for development and I have to reboot very regularly. > > I'm unsure what causes this issue so I haven't posted it as a bug yet. > I know other people are experiencing it. Just want to know if anyone > else who gets it knows why it happens, whether it is a known bug, and > most importantly if there's any workaround? > > Thanks in advance! > Cameron -- 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. -- 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.
