> 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.
> 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. > 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?
-- 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.
