-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[wasm][aot] RangeError: Maximum call stack size exceeded
in System.Text.RegularExpressions.Tests
#61756
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsSeen on
|
cc @vargaz |
cc @radekdoulik |
Line 54 in 25237fa
|
cc @lambdageek |
@lewing @radical Is this test actually expected to recurse deeply? There's not a bug where the test is unintentionally getting into an infinite recursion? It looks like in this case we overflowed in a method called from the wrapper to do a stack walk. Maybe those are expensive on wasm? In any case, maybe we can double runtime/src/mono/mono/metadata/icall.c Lines 118 to 120 in c159108
(I checked and it seems like the stack bounds computation will get non-fake values on Emscripten - so doing this stack check should work) |
I can't tell which test in particular this is from the log, but we do have some regex tests meant to stress recursive processing by analyzing really deeply-nested expressions, e.g. "((((((((((((((((((((((((((a)))))))))))))))))))", except much, much more nesting. The code has calls to TryEnsureSufficientExecutionStack on code paths that recur, and this is being triggered from one of those. |
@radekdoulik please see if you can get the stack check functioning properly. |
The error changed, now it's out of memory on Win and Linux: #71126 (comment). When running with
|
this is a build error, and the error in the issue description is when the tests are run. |
Seen on
main
rolling build:Build
Log
The text was updated successfully, but these errors were encountered: