[issue40883] parse_string.c: free "str"

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue40883] parse_string.c: free "str"

miss-islington added the comment: New changeset 79e6c15aed9b4b50efd39ddaf1dc40c374b51213 by Miss Islington (bot) in branch '3.9': bpo-40883: Fix memory leak in fstring_compile_expr in parse_string.c (GH-20667) https://github.com/python/cpython/commit/79e6c15aed9b4b50efd39ddaf1dc40c374b51213

[issue40883] parse_string.c: free "str"

Change by miss-islington : -- nosy: +miss-islington nosy_count: 3.0 -> 4.0 pull_requests: +19886 pull_request: https://github.com/python/cpython/pull/20669 ___ Python tracker _

[issue40883] parse_string.c: free "str"

Pablo Galindo Salgado added the comment: New changeset a54096e30523534e8eebb8dc1011b4536ed237a8 by Pablo Galindo in branch 'master': bpo-40883: Fix memory leak in fstring_compile_expr in parse_string.c (GH-20667) https://github.com/python/cpython/commit/a54096e30523534e8eebb8dc1011b4536ed237a

[issue40883] parse_string.c: free "str"

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +19884 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20667 ___ Python tracker __

[issue40883] parse_string.c: free "str"

New submission from Stefan Krah : Also in test_decimal, there's a small leak here: ==10040== 24 bytes in 1 blocks are definitely lost in loss record 549 of 5,095 ==10040==at 0x4C2DE56: malloc (vg_replace_malloc.c:299) ==10040==by 0x643B33: fstring_compile_expr (parse_string.c:594) ==10