On Wed, Sep 23, 2009 at 7:02 PM, Jens Alfke <[email protected]> wrote: > > On Sep 23, 2009, at 12:32 AM, Mads Sig Ager wrote: > >> another thing you should be aware of is that DOM nodes are only >> collected on full garbage collections. In order to see what is >> actually live at the end of a test, you have to force a number of GCs. > > But the GC should happen automatically after the tab's been idle for a > little while, shouldn't it? I've left the tab open for several minutes and > seen only minor reductions in memory use.
A full GC does indeed occur in idle notifications. Some of the structures that are set up are so complex that it actually takes more than one GC to get rid of them. To know for sure if it is a leak or if it is 'just' late collection it is a good idea to force more GCs explicitly. > The specific issue I'm tracking down seems to be triggered by opening child > windows, i.e. a single renderer with multiple tabs. It looks as though > closing any of the child tabs doesn't trigger a full GC; does this seem like > a good thing to add? Adding explicit GC calls are usually never a good idea. I'd like to check whether it really is a leak first. If it is a leak, we cannot get rid of it no matter how many GCs we force. > Here's the reduced test case I'm using: Thanks. I'll have a look at it tomorrow. Cheers, -- Mads --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
