All I did was enabling and disabling firebug, everything else were the same
On Wed, Jan 9, 2013 at 8:30 AM, Jan Honza Odvarko <[email protected]> wrote: > Do you have any steps/instructions we could use and reproduce the leak on > our machines? > > Honza > > > On Tuesday, January 8, 2013 4:41:28 PM UTC+1, Bill wrote: > >> I have memory problem with FireBug also. >> I disabled all my addons except FireBug and Web Developer, the memory >> usage for FF is 1,417,832K (file FFmemoryUsageWithFireBugEnable**d). >> If I disabled FireBug also,the memory usage for FF dropped to >> 183,384K(file FFmemoryUsageWithFireBugDisabl**ed). >> >> Once I enabled FireBug, my FF crashed a lot because running out of memory. >> >> >> On Friday, December 28, 2012 8:13:36 PM UTC-5, Simon Lindholm wrote: >>> >>> So apparently hundreds of instances of >>> chrome://browser/content/**pageinfo/pageInfo.xul >>> are kept alive... >>> >>> I haven't heard anyone else complain about this and Firebug certainly >>> doesn't explicitly touch pageInfo.xul, so it seems like a safe bet that >>> some other addon contributes to the problem. Can you try binary-searching >>> which one(s)? I.e. disable some suspect addons, restart, see if the problem >>> is still there, continue disabling/enabling addons, etc., until you can pin >>> it down to a single addon that makes the difference (hoping that there is >>> one). >>> >>> Simon >>> >>> Den söndagen den 23:e december 2012 kl. 08:35:38 UTC+1 skrev >>> [email protected]: >>>> >>>> Thanks for the help Sebastian. I did some new tests (based on your >>>> suggestions) and still my FF grows in memory usage. Firebug is definitely >>>> deactivated. Right now my FF is using between 732MB and 841MB of RAM with >>>> no tabs open (i am using a different browser to write this). It will >>>> continue to rise as i move around sites in that browser. This memory issue >>>> seems to only arise when Firebug is opened at least once and then >>>> deactivated...then over time memory will slowly rise and then begin to >>>> build momentum until the entire browser becomes unusable. I did an >>>> *about:memory >>>> *and have attached a zip file of it for you to check out. I also >>>> clicked the "GC" and "CC" buttons at the bottom of that page in hopes of >>>> clearing unused memory but that did not help. >>>> >>>> When the firebug add-on is disabled in FF and i restart FF i notice >>>> this memory issue never occurs. I also tested it under a new profile. >>>> Same issue. So it appears it is a firebug issue. >>>> >>>> Any other ideas will be awesome. Besides that i may have to remove the >>>> add-on entirely and find something else (fsm god help me) >>>> >>>> >>>> On Friday, December 21, 2012 6:13:52 PM UTC-5, Sebastian Zartner wrote: >>>>> >>>>> By default you need to explicitly activate Firebug for every website. >>>>> So its footprint is normally minimal. >>>>> So please first check if Firebug is really deactivated. I.e. the >>>>> Firebug icon must be gray. If that's not the case, make sure that the >>>>> option *On for All Web >>>>> Pages*<https://getfirebug.com/wiki/index.php/Start_Button>is deactivated. >>>>> When you deactivated Firebug and closed all the tabs except one, open >>>>> a new tab and enter about:memory as address. Do you see there >>>>> addresses of the tabs you already closed? >>>>> What happens if you deactivate Firebug via the Add-ons Manager and >>>>> repeat the steps? Can you see the same memory increase on a new >>>>> Firefox >>>>> profile<https://getfirebug.com/wiki/index.php/Install_Firebug_into_a_clean_profile> >>>>> ? >>>>> >>>>> Sebastian >>>>> >>>>> On Friday, December 21, 2012 1:04:37 PM UTC+1, [email protected] wrote: >>>>>> >>>>>> After several different tests with Firefox 17.0.1 (32-bit) w/ Firebug >>>>>> 1.11.1 on a Core i5 system (8GB RAM) if i power on Firebug and then power >>>>>> off and then begin surfing around the net then about 1 hour later i >>>>>> notice >>>>>> memory usage of Firefox climbs above 600MB even when all tabs have been >>>>>> shut down. This memory footprint then continues to climb over time and >>>>>> webpages and browser menus begin to bog down to a crawl. >>>>>> >>>>>> It appears Firebug may think it should be running on every webpage i >>>>>> visit and i guess processing the information and all this data is slowing >>>>>> things down. I tried the plugin on a different slower system (Core 2 >>>>>> Duo) >>>>>> and Firebug did not have the problem. I also tried using Waterfox >>>>>> (64-bit >>>>>> Firefox) and noticed the memory footprint did continue to rise when >>>>>> Firebug >>>>>> was accessed and shutdown but the bogging down wasnt as noticeable likely >>>>>> because of the 64-bit pipelining. >>>>>> >>>>>> Can someone check to see if there is a fix for this? I'd love to >>>>>> provide some debug details but no clue how to do that. Please give me a >>>>>> step-by-step on what you need from me and i will be happy to provide it. >>>>>> >>>>> -- > 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 > https://groups.google.com/forum/#!forum/firebug > -- 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 https://groups.google.com/forum/#!forum/firebug
