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 neologix
Recipients BreamoreBoy, flub, loewis, neologix, pitrou, sable, tim.peters
Date 2011-04-29.17:19:48
SpamBayes Score 1.1059619e-05
Marked as misclassified No
Message-id <>
Even worse than that, mixing to malloc implementations could lead to trouble.
For example, the trimming code ensures that the heap is where it last set it. So if an allocation has been made by another implementation in the meantime, the heap won't be trimmed, and your memory usage won't decrease. Also, it'll increase memory fragmentation.
Finally, I've you've got two threads inside different malloc implementations at the same time, well, some really bad things could happen.
And there are probably many other reasons why it's a bad idea.
Date User Action Args
2011-04-29 17:19:54neologixsetrecipients: + neologix, tim.peters, loewis, pitrou, sable, flub, BreamoreBoy
2011-04-29 17:19:54neologixsetmessageid: <>
2011-04-29 17:19:48neologixlinkissue3526 messages
2011-04-29 17:19:48neologixcreate