I have embedded V8 into a server application as a request processing mechanism. Only one request is ever touching the V8 engine at any given time, so I'm not concerned with multi-threading. However, each request is processed by it's own thread. It seems that any time a thread that is not the main thread tries to call JS code, a stack overflow exception is thrown.
This does not happen on windows, and it does not happen with V8 versions 1.3.13.5 and lower. It does happen on linux, with V8 versions 1.3.14 and higher. Due to the change log between those versions, I understand that I can call SetResourceConstraints before calling into V8. However, the docs say that default values will be used if this isn't called, and I'm concerned because the default values for new threads seem to be different from the default values used by the main thread. Can somebody on this list help me out by either providing an example of correct, threaded usage of SetResourceConstraints or by explaining why this is a bad idea? Thanks! Sincerely, Tom Brown -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
