[Dune] memory loss with matrix operator in dune-disc

[Markus Blatt]

Hi,

On Tue, Jun 24, 2008 at 03:38:38PM +0200, Chamakuri Nagaiah wrote:

> I realized that there is a memory loss problem in the matrix operator.  
> For example I have tested the testadaptivity.cc problem in dune-dd  
> using valgrind debugger and copied the debugging summary .
> I ran the simulation with different number of iterations as following...
> 
> 1) ./valgrind-3.3.0/bin/valgrind ./testadapt alusimplex 1 local  
> nopicture 0.0025 0.1
> summary for the valgrind :
> ==21340==    definitely lost: 37,344 bytes in 8 blocks.
> ==21340==      possibly lost: 0 bytes in 0 blocks.
> ==21340==    still reachable: 0 bytes in 0 blocks.
> ==21340==         suppressed: 0 bytes in 0 blocks.
> 
> 2) ./valgrind-3.3.0/bin/valgrind ./testadapt alusimplex 2 local  
> nopicture 0.0025 0.1
> summary :
> ==21461==    definitely lost: 132,264 bytes in 20 blocks.
> ==21461==      possibly lost: 0 bytes in 0 blocks.
> ==21461==    still reachable: 0 bytes in 0 blocks.
> ==21461==         suppressed: 0 bytes in 0 blocks.
> 
> 
> 
> 3) ./valgrind-3.3.0/bin/valgrind ./testadapt alusimplex 3 local  
> nopicture 0.0025 0.1
> 
> summary :
> ==21674==    definitely lost: 303,888 bytes in 32 blocks.
> ==21674==      possibly lost: 0 bytes in 0 blocks.
> ==21674==    still reachable: 0 bytes in 0 blocks.
> ==21674==         suppressed: 0 bytes in 0 blocks.
> 
> 
> 
> 4) ./valgrind-3.3.0/bin/valgrind ./testadapt alusimplex 4 local  
> nopicture 0.0025 0.1
> summary :
> ==21678==    definitely lost: 563,280 bytes in 44 blocks.
> ==21678==      possibly lost: 0 bytes in 0 blocks.
> ==21678==    still reachable: 0 bytes in 0 blocks.
> ==21678==         suppressed: 0 bytes in 0 blocks.
> 
> 
> if I increase the number of iterations, then memory lost increases  
> subsequently.
>

Judging from the output you posted I cannot comprehend why this leak is ought
to be in the matrix operator.

 
> I tried to figure it out but did not succeed. I would appreciate
> your response.
> 

Try 

man valgrind

to find out which options have to be provided for more detailed
information.

Hint: --leak-check=yes --show-reachable=yes

Cheers,

Markus