-
-
Notifications
You must be signed in to change notification settings - Fork 32k
[3.13] gh-122695: Fix double-free when using gc.get_referents
with a freed _asyncio.FutureIter
#122837
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
Conversation
I think it's worth including the test case from #122834 |
Oh yeah, forgot to add that here as well. It's there now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Changes in the 3.13 branch currently need approvals from two core devs. |
@colesbury, could you take a look? |
Thanks @ZeroIntensity for the PR, and @kumaraditya303 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
Sorry, @ZeroIntensity and @kumaraditya303, I could not cleanly backport this to
|
GH-122859 is a backport of this pull request to the 3.12 branch. |
… with a freed `_asyncio.FutureIter` (python#122837) * Backport python#122834 for 3.13 (cherry picked from commit e8fb088)
CC @colesbury