[mvapich-discuss] MPI_Comm_dup problem

[Krishna Chaitanya Kandalla]

Ingo,
         As Dave indicated on the MPICH2 list, the problem might be due 
to a missing MPI_Comm_free function. You had indicated that you are 
using MVAPICH2 1.2, which is quite old. You can try running your 
application with our latest version - MVAPICH2 1.4.1 and see if things 
are any different.

Thanks,
Krishna

Ingo Bojak wrote:
> Hi all,
>
> I'm running a routine from a parallel library (not my code, no access 
> to the source), which in its call requires a pointer to a 
> communicator. Everything works fine for many calls, when suddenly the 
> program crashes with
>
> Fatal error in MPI_Comm_dup:
> Other MPI error, error stack:
> MPI_Comm_dup(216)..: MPI_Comm_dup(comm=0x84000005, 
> new_comm=0x7fffffffdfb0) failed
> MPIR_Comm_copy(655): Too many communicators
>
> which makes we wonder if the library is missing a MPI_Comm_free call 
> somewhere? If so, I don't see how I can fix that from the outside.
>
> If someone has a suggestion for a workaround, that would be highly 
> appreciated. Perhaps one can somehow reset the communicators without 
> destroying the current MPI_COMM_WORLD? Or perhaps one can make 
> MVAPICH2 allow (a lot) more communicators... System: Intel icc 
> 11.0/083, Intel MKL 10.2.1.017, MVAPICH2 1.2.
>
> Best,
> Ingo
>
> _______________________________________________
> mvapich-discuss mailing list
> mvapich-discuss at cse.ohio-state.edu
> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
>
>