[petsc-users] memory leaks

[Luke Bloy]

Hi,

I've had some issues with petsc and slepc recently where functionality 
would stop working following a recompilation of my code, after unrelated 
code was changed. This suggested to me a memory leak somewhere.

After some investigation, it seems that there is a leak in 
petscInitialize, seemingly coming from openmpi. I'm attaching the output 
of valgrind and a basic executable calling petsciInitialize() and 
petscFinalize. I'm running on this an ubuntu 10.04 machine with petsc 
3.0.0 and openMPI (1.4.1) installed from the repositiories. Although 
this problem is also evident on machines with petsc(3.0.0) and mpi(1.3)  
installed from source.

Is this a problem others are seeing? what is a stable combination of 
petsc and mpi? how best should i proceed in tracking this down.

Thanks for the input.
Luke
-------------- next part --------------
A non-text attachment was scrubbed...
Name: petscInitTest.cxx
Type: text/x-c++src
Size: 303 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20101013/bb33dcb9/attachment.cxx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: petscValgrind.log
Type: text/x-log
Size: 2039 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20101013/bb33dcb9/attachment.bin>