On Fri, 11 Mar 2016, Roy Stogner wrote:

> On Fri, 11 Mar 2016, Manav Bhatia wrote:
>
>>  From the current status of the code in parallel.h, it looks like
>>  mpi_comm_free is called only when _I_duped_it is true, which is
>>  true only when Communicator::duplicate() is called.
>>
>>  I think the communicator created using split() also needs to be
>>  destroyed using comm_free. But since _I_duped_it is not set to true
>>  with split(), it does not seem like comm_free would be called when
>>  the communicator goes out of scope.
>>
>>  I would appreciate if someone could confirm this.
>
> This appears to be correct.  In my defense, some of the MPI
> documentation examples don't free the results of an MPI_Comm_split
> either.  In the offense, others of the MPI examples do free the
> MPI_Comm_split output, and I probably should have read through more
> than one example before writing the code.
>
> I'll put in a PR to fix it now.

Take a look at https://github.com/libMesh/libmesh/pull/865 for me?

Thanks again,
---
Roy

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to