You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 bpo-46857).
At issue are the Unicode objects created by deepfreeze and the 1-character strings (ordinals < 256).
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 bpo-46857).
Good job to discover this single leaking memory allocation!!!
Activity
jkloth commentedon Mar 21, 2022
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 bpo-46857).
At issue are the Unicode objects created by deepfreeze and the 1-character strings (ordinals < 256).
vstinner commentedon Mar 22, 2022
New changeset 88872a2 by Jeremy Kloth in branch 'main':
bpo-47084: Clear Unicode cached representations on finalization (GH-32032)
88872a2
vstinner commentedon Mar 22, 2022
Good job to discover this single leaking memory allocation!!!