-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
mono_os_mutex_destroy: pthread_mutex_destroy failed #97565
Comments
Stack trace:
So it's eventpipe cleanup. I think we saw somethign similar recently... |
Might be related to #85960 (comment) |
The callstack pasted above is not related to #96936, this is crashing in |
@lambdageek would you mind taking a second look and/or provide pointers to @davmason for next steps? |
Next steps are to do less cleanup in
I'm not sure what Johan had in mind, but one possiblity is just to call |
@lambdageek, I spent a little time looking at the mono code and I can't convince myself that |
@davmason you're probably not missing anything. I don't think we have a way to know when all the existing managed threads are really stopped/gonge (we used to have My suggestion was more "best effort" - if we know we haven't started shutting down at all, don't even try to do any cleanup in |
Probably off-topic here, but we could kill all threads on emscripten via JavaScript, if we are on UI thread. I'm working on it here @lambdageek |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=542041
Build error leg or test failing: tracing/runtimeeventsource/nativeruntimeeventsource/nativeruntimeeventsource.cmd
Pull request: #97553
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=542041
Error message validated:
mono_os_mutex_destroy: pthread_mutex_destroy failed with "Resource busy" (16)
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 1/26/2024 5:28:29 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: