Firebug memory leak

156 views
Skip to first unread message

ctecha

unread,
May 2, 2011, 11:53:27 AM5/2/11
to Firebug
Firebug is the best tool in Firefox but it keeps eating up gigs of
memory on my computer. I have the net panel, console panel, and script
panel disabled so I'm only using the HTML and CSS features and it
continually increases memory usage throughout the day. I've gotten up
to 1.2 gigs of memory being used without that many tabs being open but
the average is around 500-700mb. Is there any way to fix this? The
only reason I use firefox is for firebug but its been causing huge
slowdown issues on the browser.

Jan Honza Odvarko

unread,
May 2, 2011, 2:26:29 PM5/2/11
to Firebug
I have found a case where memory leak is caused by opening and closing
a popup/browser window (I am now looking for the reason/fix).

I would be curious if you see any leaks when using just one browser
window.

Honza

John J Barton

unread,
May 2, 2011, 2:26:27 PM5/2/11
to Firebug
Based on the information we have, which is imperfect to be sure, we
believe this is caused by a Firefox bug,
https://bugzilla.mozilla.org/show_bug.cgi?id=638075

The short version is that Firebug is monitoring net traffic because
this net traffic comes before we know if you want to use it in
debugging or not. Once we look at the traffic we cannot stop
accumulating data because of the Firefox bug. The common case where
people see this is to have firebug installed in a browser that they
also use to access large resources like video.

You can run two copies of Firefox using -no-remote and in one copy
have a profile with only debug tools. In that copy you don't watch
videos and in the other copy you don't install Firebug.

jjb

ctecha

unread,
May 9, 2011, 1:25:49 PM5/9/11
to Firebug
Thanks for the heads up. I wonder if this bug has been mentioned to
mozilla yet or not to be fixed because you guys can't fix it on your
end until they do right?

On May 2, 6:26 pm, John J Barton <johnjbar...@johnjbarton.com> wrote:
> Based on the information we have, which is imperfect to be sure, we
> believe this is caused by a Firefox bug,https://bugzilla.mozilla.org/show_bug.cgi?id=638075

John J Barton

unread,
May 9, 2011, 10:27:50 PM5/9/11
to Firebug
Please read issue 3123 and the bugzilla entry linked there.
http://code.google.com/p/fbug/issues/detail?id=3123

jjb
Reply all
Reply to author
Forward
0 new messages