Comment #5 on issue 1764 by [email protected]: Stack Size issues in Windows
http://code.google.com/p/v8/issues/detail?id=1764
Thank you very much for this explanation.
The proposal of increasing the reserved stack space of the d8 or node
exeutable using the editbin tool works like a charm.
Your explanation of the issue fits exaclty my observations:
Given d8 with reserved stack of 1MB
d8 stackoverflow.js -> maximum recursion error
d8 --stack-size=2048 stackoverflow.js -> d8 crashes at runtime when stack
overflows
d8 --stack-size=4096 stackoverflow.js -> assertion hits, d8 crashes at
startup
The second case is very hard for the user to debug. He has no clue that the
crash is caused by the stack-size he sets.
In my opinion it would be very good if there is some better error
detection/handling in that case.
Isn't it possible to get the available/reserved stack size inside a windows
process?
V8 shouldn't crash if the user sets some (valid) command line option.
Is there a documentation about v8 command line options?
Can this behaviour be added to the documentation?
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
