memory leak in backend->solve() #8

prudhomm · 2013-02-03T20:13:17Z

Original author: [email protected] (March 12, 2012 16:12:29)

What steps will reproduce the problem?

destroy and re-create the backend at each time iteration

memory grows after each delete/construct

VD: create a testcase to reproduce

Original issue: http://code.google.com/p/feelpp/issues/detail?id=8

check for leaks in PETSc in test_solve_leak now clear properly solvers before rebuilding a backend, it ensures that not only the preconditioners but also the petsc solvers (lineat and non-linear) are destroyed

…ow clear properly solvers before rebuilding a backend, it ensures that not only the preconditioners but also the petsc solvers (lineat and non-linear) are destroyed

check for leaks in PETSc in test_solve_leak now clear properly solvers before rebuilding a backend, it ensures that not only the preconditioners but also the petsc solvers (lineat and non-linear) are destroyed

…ow clear properly solvers before rebuilding a backend, it ensures that not only the preconditioners but also the petsc solvers (lineat and non-linear) are destroyed

prudhomm closed this as completed Feb 3, 2013

Trophime mentioned this issue Feb 18, 2013

doc/manual/adapt crash on develop branch #85

Closed

Doyeux mentioned this issue Jun 25, 2013

create submesh crashes in parallel #137

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

memory leak in backend->solve() #8

memory leak in backend->solve() #8

prudhomm commented Feb 3, 2013

memory leak in backend->solve() #8

memory leak in backend->solve() #8

Comments

prudhomm commented Feb 3, 2013