> The patch wasn't merged into mainline, partly because several people > pointed out that you can use a malloc replacement library (tcmalloc, > jemalloc, etc) instead. Then you still call malloc/free/etc in the 0mq > code. I experimented with this a bit, and it actually seemed pretty > brittle, at least on Mac OS X - it seems like something allocates memory > using the system malloc before loading in the malloc replacement, which > causes problems when that memory is freed at the end. I didn't really > follow up on this (other things were more urgent), but my hunch is that an > actual allocation/swapper API would be less troublesome.
I agree; it is nice to be able to use a malloc replacement, but a user-defined allocator gives you more flexibility to do whatever you require in a particular application. Same thoughts apply to the mechanism to swap to a file. -- Gonzalo Diethelm _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
