Comment #8 on issue 3060 by clearscr...@gmail.com: V8 3.23.1 and later do
not honor v8::V8::IgnoreOutOfMemoryException()
http://code.google.com/p/v8/issues/detail?id=3060
We've done some further testing with the program attached above. On 32-bit
Windows, even when we don't specify any V8 heap limits, our fatal error
handler, when invoked, is able to allocate and fill a 128 MiB block of
memory successfully. Killing the process is clearly completely unnecessary.
Maybe at some point in the past a V8 OOM condition reflected the actual
state of the process. It's still debatable whether a library should ever
kill the host, but we digress. Nowadays, with isolates and resource
constraints, it is clearly inappropriate for V8 to *ever* kill the process.
--
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
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
