Updates:
        Status: WorkingAsIntended

Comment #3 on issue 1764 by [email protected]: Stack Size issues in Windows
http://code.google.com/p/v8/issues/detail?id=1764

I'm afraid we can't allocate more stack size than what the OS is giving us.
The --stack-size flag only sets the self-imposed limit on V8's stack use (in our StackGuard class), so it can be used to restrict the stack usage, but not increase it above the OS imposed limit. On Windows, I believe the default reserved stack size is 1Mb (we try to compile, e.g., d8 with a 2Mb stack in 64-bit mode, but in 32-bit mode it should be the OS/Compiler's default size).

To get a bigger stack, you'll need to change the compiling of node.js to provide a bigger stack (using the /STACK linker flag). The system stack can't be extended programmatically after the program has started, because there might not be (and generally isn't) room below the reserved stack memory area.

You might be able to change the requested stack size of the Windows executable directly in the binary if you have Visual Studio installed, using the "editbin" tool (but I haven't actually tried that).

--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev

Reply via email to