On Jan 7, 2:26 am, Sworddragon <[email protected]> wrote: > I could successfully created the script. I have tested it 1 hour
But as I tried to explain before, this kind of test is not useful. There are almost no tools to find a memory leak. The only way I have been successful in the past is by trial-and-error: 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. So we need a test that provides an answer in at most 2 minutes. Otherwise the procedure is not practical. 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.
