So Firebug 1.9 is coming out soon, and bugfixing is top priority.
Firebug does some interesting things in order to follow requests, keep a handle on DOM nodes, etc., but most of these things use APIs that were not designed for us, aren't well know, maybe even undocumented. Let's just say that the chances of an bug like a stray reference or event listener are quite possible, resulting in memory being held and never released by the garbage collector.
So we are looking for volunteers to do the real work: start with a clean profile, no other extensions, and show us a STR (steps to reproduce). You and millions of others will reap the benefits. A nice stocking stuffer for sure!
FireClosure is one of the Firebug extensions that should certainly deserve more attention. It’s nicely integrated within the existing Firebug UI (we are actually thinking of building the extension directly into Firebug) and its purpose is to inspect JavaScript closures.
Firebug does some interesting things in order to follow requests, keep a handle on DOM nodes, etc., but most of these things use APIs that were not designed for us, aren't well know, maybe even undocumented. Let's just say that the chances of an bug like a stray reference or event listener are quite possible, resulting in memory being held and never released by the garbage collector.
So we are looking for volunteers to do the real work: start with a clean profile, no other extensions, and show us a STR (steps to reproduce). You and millions of others will reap the benefits. A nice stocking stuffer for sure!
http://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug!