Hi,
  I've noticed that there is a PetscViewer object which is not being
freed (according to log_summary).
This is not an object being created by the user, as the simplest petsc
program containing just PetscInitialize() PetscFinalize()
also displays this memory leak.

Not sure when this snuck in, but I noticed it a month back and it is
still present in the latest version I pulled yesterday.

Cheers,
  Dave

Reply via email to