> The only other way I can imagine that Firebug memory would scale with > HTML content would be if the window object itself is not being deleted > by Firefox because Firebug holds at reference to it somewhere.
Is there a way to figure this out? Something like telling the GC to flush itself a couple of times and see how many windows are still around? I happen to see this memory increase thing, and the long pause issue where Firefox will hang for a couple of seconds before I see what I was typing or scrolling starts to work. At that point I know I should restart Firefox. ;) Unfortunately, I can get to this point several times a day, not once every several days. Also, on a tangent, the jetpack project had a module to count memory references (it needed a c++ module to do so), and it was broken out into a separate add-on for Firefox 3.5 (no 3.6 yet): https://addons.mozilla.org/en-US/firefox/addon/14666 https://wiki.mozilla.org/Labs/Memory_Profiler http://hg.mozilla.org/users/avarma_mozilla.com/memory-profiler/ I'm curious if Firebug or Chromebug could repurpose it for its own needs...
-- 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.
