Comment #13 on issue 16821 by [email protected]: Memory leak http://code.google.com/p/chromium/issues/detail?id=16821
I would blame v8 for this (but would really appreciate if you double check my reasoning). The work around for crash on windows: run leak.htm in background tab. That switches on IdleHandler which would regularly invoke v8::IdleNotification() and MallocExtension::Scavenge. Now why it's not tcmalloc: 1) I tried JEMALLOC and problem still persists; 2) more directly: if I comment out v8::IdleNotifciation() in RenderThread::IdleHandler(), putting tab with leak.htm into background doesn't help. My immediate hypothesis: v8 heap grows too high due to fast wrapper allocation rate-- -remember that leaking version differs from normal just accessing div.firstChild.firstChild which creates a wrapper JS object. And v8::IdleNotification forces GCes which should eventually free those. Would report my findings. -- 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 -~----------~----~----~----~------~----~------~--~---
