➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author christian.heimes
Recipients christian.heimes
Date 2013-06-30.17:00:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372611656.54.0.917364518453.issue18333@psf.upfronthosting.co.za>
In-reply-to
Content 
Unpickler_set_memo() has a memory leak when it is called with an empty dictionariy as argument

- PyDict_Check(obj) is true
- PyDict_Size(obj) returns 0
- _Unpickler_NewMemo(new_memo_size) calls PyMem_MALLOC(0)
- PyMem_MALLOC(0) returns a valid pointer although 0 bytes have been requested
- later on an error occurs: goto exit
- because new_memo_size == 0, PyMem_FREE(new_memo) is never executed

CID 983308 (#1 of 1): Resource leak (RESOURCE_LEAK)
leaked_storage: Variable "new_memo" going out of scope leaks the storage it points to.
History
Date User Action Args
2013-06-30 17:00:56christian.heimessetrecipients: + christian.heimes
2013-06-30 17:00:56christian.heimessetmessageid: <1372611656.54.0.917364518453.issue18333@psf.upfronthosting.co.za>
2013-06-30 17:00:56christian.heimeslinkissue18333 messages
2013-06-30 17:00:56christian.heimescreate