This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: PyFrameObject.f_gen can be left pointing to a dangling generator
Type: Stage: resolved
Components: Interpreter Core Versions: Python 3.6
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: arigo, python-dev
Priority: normal Keywords: needs review, patch

Created on 2016-08-20 09:42 by arigo, last changed 2022-04-11 14:58 by admin. This issue is now closed.

File name Uploaded Description Edit
patch2.diff arigo, 2016-08-20 09:42 review
Messages (2)
msg273200 - (view) Author: Armin Rigo (arigo) * (Python committer) Date: 2016-08-20 09:42
PyFrameObject.f_gen is a pointer (not a reference) to a generator/coroutine object.  But the latter doesn't always correctly clean it up when it dies.  This pointer is used by frame.clear().

Here is an example I made, which ends in a segfault.  This example assumes we apply the patch of issue27811 first, otherwise it just crashes earlier in the same way as issue27811.

    # execute this with "python -Werror"
    import gc
    async def f():
    cr = f()
    frame = cr.cr_frame
    del cr
    # create some randomness to reuse the memory just freed by 'cr'
    import asyncio

Patch attached.  No test, but you can copy the above example.
msg274410 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2016-09-05 17:41
New changeset 3e4452424f9b by Benjamin Peterson in branch '3.5':
clear out f_gen during generator finalization (closes #27812)

New changeset 1d7a938b1e47 by Benjamin Peterson in branch 'default':
merge 3.5 (#27812)
Date User Action Args
2022-04-11 14:58:35adminsetgithub: 71999
2016-09-05 17:41:15python-devsetstatus: open -> closed

nosy: + python-dev
messages: + msg274410

resolution: fixed
stage: resolved
2016-08-20 09:42:54arigocreate