Can you break that down to a simple test case <https://getfirebug.com/wiki/index.php/Creating_a_Test_Case> with steps to reproduce? You may also analyze the memory usage via about:memory.
Sebastian On Tuesday, September 30, 2014 9:41:38 PM UTC+2, Brian wrote: > > Hello, > > I hope this is the place to report bugs and issues for Firebug... > > I'm still having issues with this release of Firebug and FF 32.0.3. When > I'm not using firebug, FF works normally with no issues and uses less than > 500mb of ram for 7 tabs. When I use Firebug to inspect an element, view the > console, etc., FF begins to use a ton of ram almost 2GBs for 7 tabs! Then > FF begins to not respond periodically and becomes very slow. The way I > have been working around this is to use firebug when I absolutely have to > and then restart FF after I'm done to free up ram and have a speedy FF. > > Thanks, > Brian > > On Saturday, September 6, 2014 1:10:52 PM UTC-4, Sebastian Zartner wrote: >> >> https://blog.getfirebug.com/2014/09/06/firebug-2-0-4/ >> >> Sebastian >> > <http://www.pinterest.com/pin/create/extension/> > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/971ce93e-970f-4b1e-9f7b-529bfb590fc8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
