New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-98925: Lower marshal recursion depth for WASI #98938
gh-98925: Lower marshal recursion depth for WASI #98938
Conversation
For (in-development) wasmtime 2.0, the stack depth cost is 6% higher. As the default is 2000 and Windows is 1000, split the difference and choose 1500 for WASI.
|
If you want to schedule another build, you need to add the " |
|
If you want to schedule another build, you need to add the " |
|
To avoid wasting resources by running the buildbots again just for a |
|
Thanks @brettcannon for the PR |
For wasmtime 2.0, the stack depth cost is 6% higher. This causes the default max `marshal` recursion depth to blow the stack. As the default marshal depth is 2000 and Windows is set to 1000, split the difference and choose 1500 for WASI to be safe. (cherry picked from commit 9711265) Co-authored-by: Brett Cannon <brett@python.org>
|
GH-98979 is a backport of this pull request to the 3.11 branch. |
…H-98979) * gh-98925: Lower marshal recursion depth for WASI (GH-98938) For wasmtime 2.0, the stack depth cost is 6% higher. This causes the default max `marshal` recursion depth to blow the stack. As the default marshal depth is 2000 and Windows is set to 1000, split the difference and choose 1500 for WASI to be safe. (cherry picked from commit 9711265) Co-authored-by: Brett Cannon <brett@python.org>
For wasmtime 2.0, the stack depth cost is 6% higher. This causes the default max
marshalrecursion depth to blow the stack.As the default marshal depth is 2000 and Windows is set to 1000, split the difference and choose 1500 for WASI to be safe.
marshal.crecursion depth limit for WASI #98925Automerge-Triggered-By: GH:brettcannon