-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
Assertion failure with multiple threads & legacy opcode tracing in free-threaded build #118415
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
cc @DinoV |
In the macOS nogil buildbot there is a slightly different assertion error that may be due to the same underlying issue:
https://buildbot.python.org/all/#/builders/1368/builds/894/steps/5/logs/stdio |
@colesbury there are multiple assertion errors that can occur with this repro, including the one from buildbot. Sometimes Python segfaults/aborts in faulthandler when trying to dump traceback. I'm not sure if it's a different issue or just Python being in some invalid state because of instrumentation version mismatch.
|
Yep, I was seeing the different variations when working on #118496. The assertions all need locks to see a consistent world view with the updates that are happening to the local events. Races against them should be relatively benign as they're asserting that we have a consistent set of events between the active monitors and the local monitors. If those race we're just delivering events longer or not long enough. But we could also hit another assertion about |
This is fixed now |
Crash report
What happened?
Bisected to 33da0e8.CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux
Output from running 'python -VV' on the command line:
Python 3.13.0a6+ (heads/main:5a90de0d4c, Apr 30 2024, 00:01:27) [GCC 10.2.1 20210110]
Linked PRs
The text was updated successfully, but these errors were encountered: