homepage

➜

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.

Recipients
Author	bob.ippolito
Date	2005年01月02日.02:22:09
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
Logged In: YES user_id=139309 Ok. I've tracked it down. realloc(...) on Darwin doesn't actually resize memory unless it has to. For shrinking an allocation, it does not have to, therefore realloc(...) with a smaller size is a no-op. It seems that this may be a misunderstanding by Python. The man page for realloc(...) does not say that it will EVER free memory, EXCEPT in the case where it has to allocate a larger region. I'll attach an example that demonstrates this outside of Python.

Content

Logged In: YES 
user_id=139309
Ok. I've tracked it down. realloc(...) on Darwin doesn't actually resize 
memory unless it *has* to. For shrinking an allocation, it does not have 
to, therefore realloc(...) with a smaller size is a no-op.
It seems that this may be a misunderstanding by Python. The man page 
for realloc(...) does not say that it will EVER free memory, EXCEPT in the 
case where it has to allocate a larger region.
I'll attach an example that demonstrates this outside of Python.

History
Date	User	Action	Args
2007年08月23日 14:28:47	admin	link	issue1092502 messages
2007年08月23日 14:28:47	admin	create