Comment #5 on issue 2638 by [email protected]: V8 Segmentation fault
http://code.google.com/p/v8/issues/detail?id=2638
I overlooked something, you don't seem to be initializing v8 at all
(although implicit initialization may occur).
Just test that script in the sample shell, d8 or node.js. If it throws an
OOM (out of memory) exception there, then your script is the problem.
I'm not sure I've seen anything recover from OOM. Chrome crashes the tab
process if JS fills the v8 heap.
Now, if you insist on running a script causing OOM and you tell v8 to
ignore OOM exceptions, you run into undefined behavior, from what I know.
JS requested more memory, there's not a single byte left, and it keeps
going on.
A segmentation fault is cute. Undefined behavior is "defined" to be capable
of anything, including wiping your entire harddrive.
--
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/groups/opt_out.
