-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
rhel-10.0
-
None
-
No
-
None
-
rhel-pt-python
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
All
-
None
I'm still seeing memory leaks when running upstream test case test_crypt under valgrind:
valgrind --leak-check=full python3 /usr/lib64/python3.12/test/test_crypt.py ... ==155009== 116,250 bytes in 2,239 blocks are definitely lost in loss record 1,623 of 1,623 ==155009== at 0x484187E: malloc (vg_replace_malloc.c:446) ==155009== by 0x49D2EF1: PyUnicode_New (in /usr/lib64/libpython3.12.so.1.0) ==155009== by 0x49F638D: ??? (in /usr/lib64/libpython3.12.so.1.0) ==155009== by 0x49E73E6: ??? (in /usr/lib64/libpython3.12.so.1.0) ==155009== by 0x49E7609: ??? (in /usr/lib64/libpython3.12.so.1.0) ==155009== by 0x49E77CD: ??? (in /usr/lib64/libpython3.12.so.1.0) ==155009== by 0x4AA8244: ??? (in /usr/lib64/libpython3.12.so.1.0) ==155009== by 0x4ACF82E: ??? (in /usr/lib64/libpython3.12.so.1.0) ==155009== by 0x49E9AA2: _PyEval_EvalFrameDefault (in /usr/lib64/libpython3.12.so.1.0) ==155009== by 0x4A0D1DD: ??? (in /usr/lib64/libpython3.12.so.1.0) ==155009== by 0x4A3AEAF: PyObject_CallMethodObjArgs (in /usr/lib64/libpython3.12.so.1.0) ==155009== by 0x4A39FE5: PyImport_ImportModuleLevelObject (in /usr/lib64/libpython3.12.so.1.0) ==155009== ==155009== LEAK SUMMARY: ==155009== definitely lost: 427,915 bytes in 8,231 blocks ==155009== indirectly lost: 0 bytes in 0 blocks ==155009== possibly lost: 0 bytes in 0 blocks ==155009== still reachable: 132,335 bytes in 3,312 blocks ==155009== suppressed: 0 bytes in 0 blocks ==155009== Reachable blocks (those to which a pointer was found) are not shown. ==155009== To see them, rerun with: --leak-check=full --show-leak-kinds=all ==155009== ==155009== For lists of detected and suppressed errors, rerun with: -s ==155009== ERROR SUMMARY: 879 errors from 879 contexts (suppressed: 0 from 0)
Issue reported before as RHEL-31770. Is this something than can be fixed?
