On Aug 6, 2008, at 12:37 PM, Jan Ploski wrote:
>> I'm using the latest of Open MPI compiled with debug turned on, and
>> valgrind 3.3.0. From your trace it looks like there is a conflict
>> between two memory managers. I'm not having the same problem as I
>> disable the Open MPI memory manager on my builds (configure option
> Thanks for the tip! I confirm that the problem goes away after
> rebuilding --without-memory-manager.
> As I also have the same problem in another cluster, I'd like to know
> what side effects using this configuration option might have before
> suggesting it as a solution to that cluster's admin. I didn't find
> an explanation of what it does in the FAQ (beyond a recommendation
> to use it for static builds). Could you please explain this option,
> especially why one might want to *not* use it?
This is on my to-do list (add this to the FAQ); sorry it isn't done yet.
Here's a recent post where I've explained it a bit more:
Let me know if you'd like to know more.