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 hunteke
Recipients amaury.forgeotdarc, hunteke
Date 2010-09-25.05:41:27
SpamBayes Score 2.2248172e-05
Marked as misclassified No
Message-id <1285393291.81.0.300634620473.issue9942@psf.upfronthosting.co.za>
In-reply-to
Content
My first thought is "Why is the reference counter stored with the object itself?"  I imagine there are very good reasons, however, and this is not an area in which I have much mastery.

Answering the question as best I can: I don't know how the reference counter is implemented in CPython, but if it's just a field in a struct, then madvise could be sent the memory location starting with the byte immediately following the reference counter.

If there's more to it than that, I'll have to back off with "I don't know."  I'm perhaps embarrassed that I'm not at all a Python developer, merely a Python application developer.  I have a few Python projects that are memory hungry, that at first glance I believe to be creating MERGEABLE objects.
History
Date User Action Args
2010-09-25 05:41:32huntekesetrecipients: + hunteke, amaury.forgeotdarc
2010-09-25 05:41:31huntekesetmessageid: <1285393291.81.0.300634620473.issue9942@psf.upfronthosting.co.za>
2010-09-25 05:41:29huntekelinkissue9942 messages
2010-09-25 05:41:28huntekecreate