[issue4872] Python will not co-exist with MFC (memory leak)

Amaury Forgeot d'Arc added the comment: - The "memory leaks" are reported in the IDE output window when the process exits; this lists all non deallocated blocks of memory. This feature is not enabled by default. Creating a CString probably initializes this feature. - Py_Finalize() doesn't f

[issue4872] Python will not co-exist with MFC (memory leak)

Changes by Terry J. Reedy : -- resolution: -> invalid status: open -> pending versions: -Python 2.5, Python 3.0 ___ Python tracker ___ __

[issue4872] Python will not co-exist with MFC (memory leak)

Martin v. Löwis added the comment: How do you know that there is a memory leak? I find it very unlikely that this interaction could cause a memory leak (although it is plausible that in this case, not all memory is returned to the system - which is something different from a memory leak). ---

[issue4872] Python will not co-exist with MFC (memory leak)

New submission from nqiang : The following code will cause memory leak in debug mode using visual studio 2008/2005 Comment out either MFC related (CString s) or Python related PY_XX. Then there will be no memory leak. #include #include int _tmain(int argc, _TCHAR* argv[]) { Py_Init