[issue26888] Multiple memory leaks after raw Py_Initialize and Py_Finalize.

STINNER Victor added the comment: That's basically a duplicate of bpo-1635741. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Py_Finalize() doesn't clear all Python objects at exit ___ Python tracker

[issue26888] Multiple memory leaks after raw Py_Initialize and Py_Finalize.

Changes by SilentGhost : -- components: +Interpreter Core -Library (Lib) nosy: +haypo, serhiy.storchaka ___ Python tracker ___

[issue26888] Multiple memory leaks after raw Py_Initialize and Py_Finalize.

New submission from Aleksander Gajewski: There are a lot of memory leaks detected by AddressSanitzer (used with gcc-6.1). The sample program with its cmakelists and output can be found in the attachment. Exact list of memory leaks is placed in log_3_python_test.txt. I am using Python3.5.1