Message134794
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:54 | neologix | set | recipients:
+ neologix, tim.peters, loewis, pitrou, sable, flub, BreamoreBoy |
2011-04-29 17:19:54 | neologix | set | messageid: <1304097594.15.0.0778335617686.issue3526@psf.upfronthosting.co.za> |
2011-04-29 17:19:48 | neologix | link | issue3526 messages |
2011-04-29 17:19:48 | neologix | create | |
|