Re: [OMPI users] Possible memory leak in opal_free_list_grow_st

2017-12-05 Thread Philip Blakely
Jeff and Nathan, Thank you for your replies; the leak doesn't happen with MPICH 3.2.1, so it's probably OpenMPI specific. I've opened https://github.com/open-mpi/ompi/issues/4567 I don't seem to be able to assign the issue but I've tagged Nathan in the comments. Kind regards, Philip On 4 Decemb

Re: [OMPI users] Possible memory leak in opal_free_list_grow_st

2017-12-04 Thread Nathan Hjelm
Have you opened a bug report on github? Typically you will get much better turnaround on issues when reported there. I, for one, don’t have time to check the mailing list for bugs but I do regularly check the bug tracker. Assign the bug to me when it is open. -Nathan > On Dec 4, 2017, at 9:32

Re: [OMPI users] Possible memory leak in opal_free_list_grow_st

2017-12-04 Thread Jeff Hammond
Try another implementation like MPICH (or derivates thereof, e.g. MVAPICH2, or Intel MPI). If you do not see the problem there, then it's pretty good evidence that it is an Open-MPI bug. In my experience, the developers of both Open-MPI and MPICH can be shamed into fixing bugs when the competing

Re: [OMPI users] Possible memory leak in opal_free_list_grow_st

2017-12-04 Thread Philip Blakely
Hello, Just following up on this from a few weeks ago since no one seems to have responded. Does anyone have any suggestions as to whether this is a genuine memory leak with OpenMPI or some other kind of problem I need to debug? For more real-world context: this was triggered by a CFD code we use