[petsc-dev] threadcomm memory leak

Jed Brown jedbrown at mcs.anl.gov
Tue Jul 17 22:14:18 CDT 2012

On Tue, Jul 17, 2012 at 10:10 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:

> But Shri indicated there is a possible problem, what is that problem? Or
> is there none?

The "problem" is that there is special code that removes the threadcomm
from SELF and WORLD. If we assume that they are different, but in fact,
SELF and WORLD are the same object, it looks like a reference counting
inconsistency. Thus special code to deal with MPIUNI where they are the
same. I don't understand why it's such a problem to make MPIUNI non-special
in having SELF and WORLD be different values.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120717/43493eba/attachment.html>

More information about the petsc-dev mailing list