For what it's worth, I downgrade to firebug-1.12.8b1.xpi, then reinstalled firebug-2.0b8.xpi and it seems to have solved the problem.Sorry I couldn't give any more information...
Sorry, they're only available on an internal network. I realize this makes it impossible to reproduce... I was just wondering if anyone else was experiencing this.
I am having the same problems.
Running a project on my local machine, Windows 7, in the last week, suddenly getting this error all over the place.
Using Firefox 30.0 and firebug 2.0.2.
Script keeps hanging and giving this message: chrome://firebug/content/lib/trace.js:55
I don't know how to downgrade firebug, where will you get a previous version?
I uninstalled it and installed again, didn't help.
On Monday, July 28, 2014 5:12:13 PM UTC+2, Hendrick Musche wrote:
Am Montag, 21. Juli 2014 20:36:41 UTC+2 schrieb Ben Record:Sorry, they're only available on an internal network. I realize this makes it impossible to reproduce... I was just wondering if anyone else was experiencing this.I am, since the last update of Firefox (31.0). With some internal projects with MooTools code, we all get blocking errors as mentioned above, especially using mootools.min. But even with google.com, the whole browser blocks for 1-2 seconds before rendering the page.
New profiles don't help. FireBug has become 98% useless for me including after a new profile followed by a complete remove-reinstall.
I suspect this has something to do with a conflict with Mozilla's built-in imitation FireBug that they call "Tools".
Tools doesn't catch js errors except sometimes.
They do, you just need to set the proper filter options:
FireBug causes FireFox to freeze for up to 30 seconds at a time. I get no response from Mozilla on this. A little google work shows that this is not exactly a rare problem - but everyone is experiencing it if they've got FF 30+.