[Digikam-devel] [Bug 131277] Memory leak in image editor

[Rainer Krienke]

Am Montag, 24. Juli 2006 08:26 schrieb Gilles Caulier:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=131277
>
>
>
>
> ------- Additional Comments From caulier.gilles free fr  2006-07-24 08:26
> ------- Hi krienke,
>
> This is certainly a memory leak. Please just re-run digiKam using valgring
> following the instructions in the HACKING file (at end). Just report the

I ran valgrind --tool=memcheck --leak-check=full --error-limit=no /opt/kde3/bin/digikam 
but there was no information in the output about  a big leak as I would have expected because of the observed decrease in free memory:

<ran through ~20 photos in image editor, then terminated digikam>
==7042== LEAK SUMMARY:
==7042==    definitely lost: 6,349 bytes in 75 blocks.
==7042==    indirectly lost: 40,174 bytes in 879 blocks.
==7042==      possibly lost: 400 bytes in 3 blocks.
==7042==    still reachable: 437,184 bytes in 7,824 blocks.
==7042==         suppressed: 0 bytes in 0 blocks.
==7042== Reachable blocks (those to which a pointer was found) are not shown.
==7042== To see them, rerun with: --show-reachable=yes


However afterwards I ran free -m then started digikam and in the imageeditor ran through 50 photos,
terminated digikam and then again ran free -m:

[krienke at bliss:~] 589 > free -m
                    total       used       free     shared    buffers     cached
Mem:          1012        687        324          0          9        571
-/+ buffers/cache:        106        905
Swap:         2055        208       1846

<run of digikam> 

[krienke at bliss:~] 589 > free -m
                   total       used       free     shared    buffers     cached
Mem:          1012        677        335          0          4        436
-/+ buffers/cache:        236        775
Swap:         2055        377       1677

In this case the usage of swap increased by ~160MB which is the strange behaviour I 
observed but valgrind does not say anything. I do not understand this. 

Next I started digikam once more again looked at the very same 50 photos in imageeditor 
and then terminated  digikam again. The free calls are again from before starting digikam 
and after terminating it:

krienke at bliss:~] 587 > free -m
                    total       used       free     shared    buffers     cached
Mem:          1012        688        323          0         10        449
-/+ buffers/cache:        228        783
Swap:         2055        375       1679

<digikam run. Looked at  50 photos in imageeditor>

[krienke at bliss:~] 588 > free -m
                   total       used       free     shared    buffers     cached
Mem:          1012        694        317          0          6        390
-/+ buffers/cache:        296        715
Swap:         2055        570       1484
 
No again another 125 MB of swap has been eaten up.

Any idea by what this behaviour might been caused?

Thanks 
Rainer
-- 
---------------------------------------------------------------------------
Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022
Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312
Mail: krienke at uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke
Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html
---------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20060724/492500fe/attachment.sig>