On Jan 7, 2:05 pm, Sworddragon <[email protected]> wrote: > > But as I tried to explain before, this kind of test is not useful. > > But the test is running automatically so you can do something else at > this time.
Not with my computer, it is pegged at 100% CPU during the test. > > > 1) Find a test case that can show the leak quickly, > > 2) Change a parameter of the test run (panel selection, panel enable, > > kind of page content, Firebug option, etc). > > 3) Look for a case where the leak does not happen. > > 4) Go to 2. > > While i was sleeping the test was running for 12 hours (1907434 > Reloads). At this test i haven't opened the firebug main panel. After > the 12 hours firefox was just using a memory amount of ~48 MB after > closing all tabs and no freezes have occured. I ran your test for 1000 rounds with Firebug closed. The memory went from 83M to 87M. Then I ran your test for 5000 rounds with Firebug open on the script panel. The memory went from 87M to 95M. If there is a leak in Firebug that amounts to <4M in 5000 reloads, then in my opinion it is not worth further investigation. Now I would guess that you are surprised or disappointed or even disbelieving by my result. So the next step is for you to create a new Firefox profile, install only Firebug 1.6a2, and repeat exactly either your test or mine. > > > So we need a test that provides an answer in at most 2 minutes. > > Otherwise the procedure is not practical. > > Just run my test 2 minutes and you will get a memory leak of 2-4 MB or > is that not enough? No because the memory reading with Firefox is not accurate to 2-4MB, it has garbage collection. 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.
