Issue 129: Memory consumption hyperoscillations http://code.google.com/p/v8/issues/detail?id=129
Comment #11 by [EMAIL PROTECTED]: Thanks for the detailed reports. The issue reported in comment 5 was a bug that has been fixed in bleeding_edge and pushed to trunk. In comment 6, you're seeing a genuine out of memory with the default fatal error handler. Clearly our GC policies don't respond well when close to the memory limit, which is why it takes almost 45 seconds just to exhaust that last little bit of memory on the last enqueue() call. We will try to adjust them to improve the situation. I can't reproduce the issue mentioned in comment 8. Is it your original test case (with the unqueue operation commented out)? -- 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 --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
