Status: Accepted
Owner: [email protected]
CC: [email protected], [email protected], [email protected]
Labels: Type-Bug Priority-Medium
New issue 3976 by [email protected]: OOM crash caused by GC not keeping up
with fragmentation
https://code.google.com/p/v8/issues/detail?id=3976
I attached a test that causes OOM in V8 even though only 14% of the heap is
used.
[29775] 3107 ms: Mark-sweep 1412.7 (1456.6) -> 163.5 (1028.6) MB, 249.3
ms [allocation failure] [GC in old space requested].
[29775] 3878 ms: Mark-sweep 626.3 (1456.6) -> 194.4 (1456.6) MB, 242.8
ms [allocation failure] [GC in old space requested].
[29775] 4168 ms: Mark-sweep 230.0 (1456.6) -> 194.4 (1456.6) MB, 241.8
ms [last resort gc].
[29775] 4474 ms: Mark-sweep 194.4 (1456.6) -> 194.4 (1456.6) MB, 305.7
ms [last resort gc].
#
# Fatal error in CALL_AND_RETRY_LAST
# Allocation failed - process out of memory
#
Attachments:
x.js 776 bytes
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
