Comment #35 on issue 16821 by [email protected]: Memory leak http://code.google.com/p/chromium/issues/detail?id=16821
Is this a case where V8 doesn't run a GC, because a GC is instigated only by memory pressure in the V8 heap, but yet, the pointers from the V8 heap prevent WebCore from being able to release its substantial amount of memory? If so, perhaps we need a way of signalling to V8 that there *is* memory pressure at some point, and that additional GCs are suddenly very worth while (to preclude a potential crash). As I recall, there is a hook in TCMalloc for calling some external function when memory pressure is about to cause an out-of-memory condition. Perhaps the V8 allocator should be notified of such a problem. -- 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 -~----------~----~----~----~------~----~------~--~---
