On Jun 26, 11:20 pm, Hancoque <[email protected]> wrote: > No, unfortunately it doesn't fix the issue. I created another test build available here: http://www.softwareishard.com/temp/firebug-1.8.0b4.memory1.xpi Could you please test it?
If it still doesn't help, the most effective next step is to put together a test case that would allow us to reproduce your scenario on our machines. The best would be probably to to use directly your profile, but not sure if it's feasible for you (the profile could contains sensitive information). The other option could be to get at least the list of open tabs, perhaps the leak comes from a specific page. The list is stored in sessionstore.js (within your profile), but again there are cookies so, could be a problem for you. Or you could try to use directly SVN revisions. There is 36 commits between Firebug 1.8b2 and b3 (Firebug is using SVN). You could find out, which one is making the difference (you need 4-5 tests to find out the right revision if you bisect in half). I am happy to assist if you need help how to download the source and install (it's very easy)! Honza -- 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.
