Skip to content
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

StackOverflowException when running Jint.Tests.CommonScripts #1017

Closed
juliandeange opened this issue Dec 2, 2021 · 7 comments · Fixed by #1025
Closed

StackOverflowException when running Jint.Tests.CommonScripts #1017

juliandeange opened this issue Dec 2, 2021 · 7 comments · Fixed by #1025

Comments

@juliandeange
Copy link

Hello,

I've been running the Unit Test projects included with the library and found out that Jint.Tests.CommonScripts fails with a StackOverflowException when using dotnet test.

Running in verbose mode it seems like the script controlflow-recursive.js is the one which is failing. If I comment out line 42 in SunSpiderTests.cs the tests are able to execute without any issues.

Is there any plan to fix this test case or could it even be removed entirely?

Thanks!

@sebastienros
Copy link
Owner

Snap, don't we run these in the CI ?

@sebastienros
Copy link
Owner

Actually we do run them and they passed.
Do you have a special environment that it fails on? What version of dotnet are you using, and are you on the main branch?

https://github.com/sebastienros/jint/runs/4385801313?check_suite_focus=true#step:4:28

@juliandeange
Copy link
Author

Im using version 5.0.303 also this is with Jint version 3.0.0-beta-2035

image

@juliandeange
Copy link
Author

This is only an issue when running the Debug configuration. Release there are no problems.

@lahma
Copy link
Collaborator

lahma commented Dec 2, 2021

Yes recursive is hard in debug mode when no inlining happens.

@juliandeange
Copy link
Author

I see. Should the Debug config be disabled when running these unit test projects then?

@lahma
Copy link
Collaborator

lahma commented Dec 11, 2021

It's now run only when it's a release build, thanks for reporting this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants