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.

Author pablogsal
Recipients amaury.forgeotdarc, arigo, ghaering, iritkatriel, jcea, lkraav, pablogsal, pitrou, pxd, vstinner
Date 2021-02-15.18:02:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
>  If the GIL is released before the tuple is fully populated and something access to this tuple via the GC (ex: gc.get_objects()), accessing the tuple can crash, especially in the Python land (for example, repr(the_tuple) is likely to crash).

It can happen even without releasing the GIL: A new tuple is created, then some other object is created using the CAPI, the gc runs, the callback triggers (or the tuplevisit method is invoked) and then kaboom
Date User Action Args
2021-02-15 18:02:33pablogsalsetrecipients: + pablogsal, arigo, jcea, ghaering, amaury.forgeotdarc, pitrou, vstinner, lkraav, pxd, iritkatriel
2021-02-15 18:02:33pablogsalsetmessageid: <>
2021-02-15 18:02:33pablogsallinkissue15108 messages
2021-02-15 18:02:33pablogsalcreate