At the moment, running my own default profile in 'usage' mode with leak gauge is pretty pointless. I get results like Leaked 9 out of 1522 DOM Windows Leaked 54 out of 2661 documents Leaked 1 out of 467 docshells Leaked content nodes in 100 out of 2805 documents but need steps to reproduce which is mostly impossible after a normal (long) session (and also for short ones if the leaked reference has a normal chrome url). So if leak gauge could also record the steps and then try to reproduce combined with reducing the number of steps. By the way, Firefox' virtual memory always growths during my sessions (uo to 1 GB and higher). Is this expected behavior?
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.