Yes of course there is a leak caused by Firebug. We store copies of everything firefox has ever seen about your page in a form that is easy to read but not compact. And we are working hard to make these leaks bigger all of the time ;-)
It is possible that Firebug is storing more information than you requested and that would be a bug. If you have a test case showing this problem I will drop everything to fix it. But the test case has to be very solid because I've done this a couple of times in the past only to discover that Firebug was being used on sites that load large images every few seconds. A good place to start is to 1) install Firebug in a new Firefox profile: http://groups.google.com/group/firebug/web/faq-about-firebug then run with two tabs: 1) http://example.org, 2) your test page. 2) Don't change any options in Firebug. 3) Look at how the memory changes. 4) Change the Firebug options on your test page. 5) Look at memory 6) exit the tab with your test page. 7) Look at memory I don't know how aggressive Firefox collects garbage so you need to cycle through the test sequence a couple times. jjb On Jan 28, 6:12 am, waterflame <[email protected]> wrote: > Believe me there's a leak somewhere and it's definitely firebug. > > If you disable firebug 1.3.0 and run firefox 3.0.5, u'll hardly hit > the 100 MB mark. > If you enable firebug with the main google page opened and leave it > for a couple of hours u'll reach 250 MB min. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
