[Digikam-devel] [Bug 180224] memory leakage in image editor?

[Richard Ash]

https://bugs.kde.org/show_bug.cgi?id=180224





--- Comment #12 from Richard Ash <richard audacityteam org>  2010-01-09 23:01:51 ---
Created an attachment (id=39727)
 --> (http://bugs.kde.org/attachment.cgi?id=39727)
Output of valigrind in massif mode (for SVN r1067737)

This is a complete massif run over two images. Same set of actions as in
comment #8, except I went back to JPEG2000 images. For this I used a check-out
of SVN r1067737 (post 1.0.0 release) because White Balance doesn't crash there.

I've since run through a longer batch of images not under Valgrind using the
same binary, to try and confirm that it has the same memory leakage issues as
we have been testing in 1.0.0. Unfortunately after 8 images the results were
inconclusive - some growth, but not enough to be certain that it's leaking as
badly as before:
%CPU    %MEM       VSZ      RSS TIME    COMMAND
16.0     4.1    1333512  169108 0:02    ./digikam/digikam/digikam
to:
%CPU    %MEM       VSZ      RSS TIME    COMMAND
23.4    24.1    2142684  981528 5:47    ./digikam/digikam/digikam

I need to do some more testing, unfortunately this will have to be parked until
Friday due to work, but I think I'll try building SVN HEAD at that point and
see if I can reproduce the original bug in that before we invest any more time
in this issue.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.