-
Notifications
You must be signed in to change notification settings - Fork 110
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
coroutine in thread XYZ has overflowed its stack
while running loom unit test
#363
Comments
UditDey
changed the title
Sep 12, 2024
coroutine on thread XYZ overflowed its stack
while running loom unit testcoroutine in thread XYZ has overflowed its stack
while running loom unit test
Did you build the test with debug build? If so, could you also try release build and check if the problem has been resolved? |
I only ran the tests in release mode, I'll give it a shot in debug mode just to try |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'm using loom to verify a lock-free data structure that I've written (I should add this is the first time I'm using loom).
I set up 3 unit tests, each one has my structure in different configurations, and then I'm using loom to verify correctness when multiple threads are interacting with the structure. My 3rd unit test is the most intensive one. It spawns the same number of threads as the others but will involve significantly more atomic ops.
I expected the 3rd case to take a lot of time, however it fails to execute entirely:
I can see this is a stack overflow but it specifies that a coroutine has had a stack overflow
Does loom use stackful coroutines? Or does
cargo test
use stackful coroutines internally? Has anyone else faced this before while running an intensive loom test?And I'll just clarify that none of my code uses stackful coroutines. In fact loom is its only dependency so this is definitely not originating in my code. Google'ing resulted in nothing and this is the first time I've seen a stack overflow error that mentions a coroutine, so I have no clue where its originating
The text was updated successfully, but these errors were encountered: