[issue47084] Statically allocated Unicode objects leak cached representations

STINNER Victor added the comment: > The newly implemented statically allocated Unicode objects do not clear their > cached representations (wstr and utf-8) at exit causing leaked blocks at exit > (see also issue46857). Good job to discover this single leaking memory allocation!!! --

[issue47084] Statically allocated Unicode objects leak cached representations

STINNER Victor added the comment: New changeset 88872a29f19092d2fde27365af230abd6d301941 by Jeremy Kloth in branch 'main': bpo-47084: Clear Unicode cached representations on finalization (GH-32032) https://github.com/python/cpython/commit/88872a29f19092d2fde27365af230abd6d301941 --

[issue47084] Statically allocated Unicode objects leak cached representations

Change by Jeremy Kloth : -- keywords: +patch pull_requests: +30122 stage: -> patch review pull_request: https://github.com/python/cpython/pull/32032 ___ Python tracker ___ ___

[issue47084] Statically allocated Unicode objects leak cached representations

New submission from Jeremy Kloth : The newly implemented statically allocated Unicode objects do not clear their cached representations (wstr and utf-8) at exit causing leaked blocks at exit (see also issue46857). At issue are the Unicode objects created by deepfreeze and the 1-character str