Comment #14 on issue 16821 by [email protected]: Memory leak http://code.google.com/p/chromium/issues/detail?id=16821
Now, that was funny---actually GC is never invoked (even Scavenge) after 1st loop which builds strings. I think that's due to the fact that we don't exhaust new space. Curious things: number of global handles grows for some reason---it's obvious why it doesn't drop---there is no GC---but I thought that we should cache everything after an iteration or two, but apparently there is something we constantly build on each iteration and cannot release due to absence of GC. And, of course, that explains why putting into background helps: v8::IdleNotification() eventually forces GC. The easy fix would be to trigger GC once in a while if too many global handles are allocated. But I'd like to understand first why number of handles grow. Still if we want something quickly, that hack is the way to go imho. Looking further. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
