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 loewis
Recipients loewis, pitrou, skrah
Date 2012-04-08.17:30:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333906256.63.0.126919248648.issue14520@psf.upfronthosting.co.za>
In-reply-to
Content
There are really two options:

a) if an object is a container, and the contained is accessible to reflection (preferably through gc.get_referents), then the container shouldn't account for the size of the contained.
b) if the contained is not accessible (except for sys.get_objects() in a debug build), then the container should provide the total sum.

A memory debugger is supposed to find all objects (e.g. through gc.get_objects, and gc.get_referents), eliminate duplicate references, and then apply sys.getsizeof for each object. This should then not leave out any memory, and not count any memory twice.
History
Date User Action Args
2012-04-08 17:30:56loewissetrecipients: + loewis, pitrou, skrah
2012-04-08 17:30:56loewissetmessageid: <1333906256.63.0.126919248648.issue14520@psf.upfronthosting.co.za>
2012-04-08 17:30:56loewislinkissue14520 messages
2012-04-08 17:30:55loewiscreate