[pypy-issue] Issue #2144: pypy win32 leaks memory (pypy/pypy)

mattip issues-reply at bitbucket.org
Thu Sep 24 20:00:17 CEST 2015


New issue 2144: pypy win32 leaks memory
https://bitbucket.org/pypy/pypy/issues/2144/pypy-win32-leaks-memory

mattip:

In addition to the memory leaks in own multiprocessing tests, like [this one](http://buildbot.pypy.org/summary/longrepr?testname=AppTestBufferTooShort.%28%29.test_exception&builder=own-win-x86-32&build=686&mod=module._multiprocessing.test.test_connection)

setting ``PYPY_ALLOC=1`` and running pypy -c "exit()" prints:

    bin\pypy.exe
    Python 2.7.10 (2e8414e8d696, Sep 23 2015, 19:34:32)
    [PyPy 2.7.0-alpha0 with MSC v.1500 32 bit] on win32
    Type "help", "copyright", "credits" or "license" for more information.
    And now for something completely different: ``PyPy development: the art of
    waiting''
    >>>> exit()
    mem.c: 14 mallocs left (most recent first):
    020FBBE0  pypy_g__ll_dict_resize_to__DICTPtr_Signed
    01D41938  pypy_g_IncrementalMiniMarkGC_major_collection_step
    01D41908  pypy_g_IncrementalMiniMarkGC_major_collection_step
    01D73BB0  pypy_g_IncrementalMiniMarkGC_minor_collection
    01D418A8  pypy_g_IncrementalMiniMarkGC_setup
    01D41848  pypy_g_ll_newdict_size__Struct_DICTLlT_Signed
    01D41818  pypy_g_IncrementalMiniMarkGC_setup
    01D417E8  pypy_g_IncrementalMiniMarkGC_setup
    01EA1C20  pypy_g_IncrementalMiniMarkGC_setup
    01EA1BF0  pypy_g_IncrementalMiniMarkGC_setup
    01EA1BB8  pypy_g_IncrementalMiniMarkGC_setup
    01EA1B88  pypy_g_IncrementalMiniMarkGC_setup
    01EA1B58  pypy_g_IncrementalMiniMarkGC_setup
    01EA2FC0  pypy_g_IncrementalMiniMarkGC_setup





More information about the pypy-issue mailing list