On 30 May 2016, at 16:32, David Ham <David.Ham@imperial.ac.uk> wrote:
Alternatively, might this be the PETSc memory leak?
I don't know, but it looks like this happens almost immediately in the run, which doesn't seem like a memory leak to me.
Lawrence