From: Denis D. <dan...@ya...> - 2003-09-27 13:05:42
|
Hmm... you are right, there is a memory leak... And it depends on how many times I make "mesh refinement->equation system reinit". Reference counting in libmesh and -log_summary option of petsc give nothing (i.e. equal numbers of created and destroyed objects). Valgrind is more careful. The full output of valgrind and ex10 is atteched. There is one message about petsc, and messages about function DofObject::set_old_dof_object(void)... I got the same errors for my programm also. Regards, Denis On Wed, Sep 24, 2003 at 05:33:45PM -0500, Benjamin S. Kirk wrote: > [I have sent this to the new libmesh-users list] > > OK, I'll get you a patch that you can try. It would be nice to have an > option to remove the nodes, I agree... This will certainly reduce the > disk space required. > > I'm still worried about the memory usage you report. is the memory > usage ~1/2 as much after 5000 time steps? ~1/4 as much after 2500 time > steps?? It seems like there could be a memory leak occuring at each > time step. Make sure you are running in debug mode & try the > -log_summary option, which will print memory usage statistics (from > PETSc) when the program quits. The program valgrind can also be > useful in finding memory leaks. > > The only reason I mention this is because I routinely work with meshes > that have on the order of 200k nodes and it doesn't require nearly that > much memory. > > I know what needs to be changed in addition to the patch you sent > earlier. I'll explain it more when I submit my patch later. > > -Ben > |