Comment #11 on issue 16107 by [email protected]: WebKit: Vector Drawing, altering stroke properties crash http://code.google.com/p/chromium/issues/detail?id=16107
First check: v8 GC is invoked, but couldn't reclaim memory back. On my box committed size grows up to 1.8G and next time GC manages to release resources. There are some cases when v8 is to blame for retention, but does anybody know if JS behaves nicely? I'd spend some more time investigating, but if some has reduced test case, it'd be very good. Good news: if it's only about huge bitmaps, there is already mechanism in place to trigger GC more often (external cost might be communicated back to v8 and easy to calculate). -- 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 -~----------~----~----~----~------~----~------~--~---
