René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Crash in asyncio when printing a task object at teardown","articleBody":"If a task object is still alive at interpreter teardown, something can try to print it. This will end in `_asyncio.Future._repr_info` that in turn calls:\r\n\r\n```\r\nreturn PyObject_CallOneArg(asyncio_future_repr_info_func, (PyObject *)self);\r\n```\r\n\r\nbut `asyncio_future_repr_info_func` at that point can be `NULL` because `module_free` of `_asynciomodule.c` has been executed already, called by `Py_FinalizeEx -\u003e finalize_modules -\u003e _PyInterpreterState_ClearModules -\u003e ... -\u003e module_dealloc`.\r\n\r\nThe crash happens in the last `_PyGC_CollectNoFail` of `finalize_modules` so somehow the task survived the first collection and then was garbage in the second one.\r\n\r\nI don;t have a simple repro for now, but you can get the failure by cloning https://github.com/Textualize/textual checking commit 5fe47da058564b72e5081a5658c054f55a5d85cd, installing the project and test deps and running `pytest`.","author":{"url":"https://github.com/pablogsal","@type":"Person","name":"pablogsal"},"datePublished":"2022-08-24T11:43:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":11},"url":"https://github.com/96232/cpython/issues/96232"}