-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Random stack overflow on windows-gnu #139070
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
Comments
That's suspicious. And it's spurious right? Even trying to build the same test doesn't always overflow? |
Yea, it's random. When I find some time, I'll try doing some stress tests to see if it is reproducible. |
FWIW, I'm also regularly seeing this problem when running This is the stack trace I get in WinDbg at the moment of the
Without debug symbols, I only have Ghidra here to make some sense of this stack trace and the addresses. CC @ehuss |
Just an update on this, I was able to reproduce it on my local machine just running I don't really know how to debug, though. 😦 Was going to try ProcDump, but this is taking too much time. |
Might be the same as #140798 which bisected the failure origin. |
In Cargo's CI we have been seeing an increase in STATUS_STACK_OVERFLOW compiling random tests on Windows-gnu. The errors look like:
These tests are generally doing trivial things.
I haven't had time yet to investigate or try to reproduce.
Example PRs with the failure:
author
field to beauthors
in book.toml cargo#15362target.'cfg(...)'
doesnt respect cfg from build script cargo#14312The text was updated successfully, but these errors were encountered: