[MERGE] BTreeIndex intern()
John Arbash Meinel
john at arbash-meinel.com
Thu Apr 9 01:44:16 BST 2009
-----BEGIN PGP SIGNED MESSAGE-----
Michael Hudson wrote:
> John Arbash Meinel wrote:
>> - From what I can tell, I think we have a small memory leak somewhere,
>> because the current 'WorkingSize' doesn't match the size of objects I
>> can access using PyMemoryDump. I feel like it is something introduced
>> recently, but I haven't found a great way to actually debug it yet.
> valgrind is pretty good at this, I think...
I tried and the output was swamped with:
==566== Use of uninitialised value of size 4
==566== at 0x808C047: PyObject_Free (obmalloc.c:929)
==566== by 0x810C25B: code_dealloc (codeobject.c:260)
==566== by 0x8099EA8: tupledealloc (tupleobject.c:170)
Now maybe I just need to suppress all PyObject_Free statements...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar