site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On 7 May 2010, at 21:30, Jens Alfke wrote:

Neither of these goes as far as overriding malloc itself. Instead they define their own allocator functions and then use those instead of calling malloc directly.

My impression is that the OP was actually talking about constructing a new default malloc() zone but using jemalloc's routines rather than the historic OS X implementation, which is what's making matters difficult. As I hinted, if it were *my* application, I'd be looking at why it's calling free() so much. If that's happening, perhaps it's allocating and releasing too much and maybe caching and re-using objects might help (for instance). Kind regards, Alastair. -- http://alastairs-place.net _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com