On Jan 11, 12:55 am, Sworddragon <[email protected]> wrote: > All 6 tests with 20000 reloads and 15000 <div>Debug</div> per reload > with every panel selected are finished. Here are the results: > > Console: 202 MB > HTML: 208 MB > CSS: 197 MB > Script: 208 MB > DOM: 205 MB > Network: 180 MB > > It seems that the amount of HTML content isn't the reason but I'm > wondering why the memory usage was inceased by only 1000 reloads. > After the 6 tests i have made 2 tests with manipulating the DOM. One > test with a call from the onload attribute of the body tag and the > other test with a call in the javascript code. At these tests i have > made 1000 nested DOM operations with attribute manipulation per > reload. After this tests the memory usage was 182 MB with a call from > the onload attribute and 190 MB with a call in the javascript code. > This memory leak isn't easy to analyze but do you have any other > suggestions?
First I suggest you double check that your current test 'scales' with the number of reloads, meaning 500 reloads gives half as much increase as 1000. Also double check the impact of disabling Console panel. If it does scale, then here are some suggestions: 1) Add an unload event handler to the page. Does not have to do anything in particular, it will just cause the page to be handled differently. 2) Include some large JS library. (I tried this but did not see any effect). 3) Add some AJAX requests to exercise the net traffic components. 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.
