[petsc-users] call to PetscViewerAsciiOpen

[Randall Mackie]

Thanks Matt. 

A call to PetscViewerDestory and MPI_Comm_free took care of all the valgrind issues.

Randy

> On Dec 21, 2018, at 11:21 AM, Matthew Knepley <knepley at gmail.com> wrote:
> 
> On Fri, Dec 21, 2018 at 2:08 PM Randall Mackie via petsc-users <petsc-users at mcs.anl.gov <mailto:petsc-users at mcs.anl.gov>> wrote:
> The attached simple test program (when compiled in debug mode with gfortran and mpich) throws a lot of valgrind errors on the call to PetscViewerAsciiOpen, as well as the call to MPI_Comm_split.
> 
> I can’t figure out if it is a problem in the code, or a bug somewhere else.
> 
> Those are all just memory leaks. I believe most will go away if you call PetscViewDestroy().
> 
>   Matt
>  
> Any advice is appreciated.
> 
> Thanks
> 
> Randy M.
> 
> 
> 
> 
> 
> 
> -- 
> What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
> -- Norbert Wiener
> 
> https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20181221/4e3e6fbb/attachment-0001.html>