On Jan 9, 1:47 am, Sworddragon <[email protected]> wrote: > On 9 Jan., 02:11, John J Barton <[email protected]> wrote: ... > I have added more HTML elements. 15000 <div>Debug</div> and the memory > usage was increasing after 1000 reloads to ~70 MB (the previous tests > without this additional HTML content was using just ~55-60 MB.
Firebug does not directly store information in proportion to the number of HTML elements. The HTML panel is created incrementally based on which elements the user has explored. Firebug does track changes to HTML via DOM Mutation events. This begins after the 'load' event. So you might try inserting elements in the onload handler. If the extra memory scaled with the number of mutation events then we'd be on to something. Might try attributes also. 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. jjb
-- 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.
