Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
gh-134679: Fix assertion failure in QSBR#134811
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This is the same underlying bug aspythongh-130519. The destructor may callarbitrary code, changing the tstate->qsbr pointer and invalidating theold _qsbr_thread_state.
Tested by running |
a4d37f8
intopython:mainUh oh!
There was an error while loading.Please reload this page.
Thanks@colesbury for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
This is the same underlying bug aspythongh-130519. The destructor may callarbitrary code, changing the `tstate->qsbr pointer` and invalidating theold `struct _qsbr_thread_state`.(cherry picked from commita4d37f8)Co-authored-by: Sam Gross <colesbury@gmail.com>
GH-134814 is a backport of this pull request to the3.14 branch. |
bedevere-bot commentedMay 27, 2025
|
Uh oh!
There was an error while loading.Please reload this page.
This is the same underlying bug asgh-130519. The destructor may call arbitrary code, changing the
tstate->qsbr
pointer and invalidating the old_qsbr_thread_state
.