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 corona10, eelizondo, gregory.p.smith, nascheme, pablogsal, pitrou, steve.dower, tim.peters, vstinner
Date 2020-04-13.22:51:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> gc.freeze() has a similar issue, no? This function also comes from Instagram specific use case ;-)

Not really because this patch is much more impacting. gc.freeze() moves objects into a permanent generation making them not participate in the GC so the only leaks are cycle-based. With this patch immortal object will leak every strong reference that they have even if they don't participate in cycles (but also if they participate in cycles).
Date User Action Args
2020-04-13 22:51:55pablogsalsetrecipients: + pablogsal, tim.peters, nascheme, gregory.p.smith, pitrou, vstinner, steve.dower, corona10, eelizondo
2020-04-13 22:51:55pablogsalsetmessageid: <>
2020-04-13 22:51:55pablogsallinkissue40255 messages
2020-04-13 22:51:54pablogsalcreate