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

[Richard Ash]

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





--- Comment #9 from Richard Ash <richard audacityteam org>  2010-01-06 23:18:22 ---
This time, just save the loaded image straight to PNG, no processing:

start off
%CPU    %MEM       VSZ      RSS TIME    COMMAND
22.7     4.1    1299936  169872 0:02    digikam
after 5 images:
%CPU    %MEM       VSZ      RSS TIME    COMMAND
48.6     7.5    1448720  307948 1:29    digikam
after 10
%CPU    %MEM       VSZ      RSS TIME    COMMAND
47.6     8.5    1480828  346508 2:57    digikam

That's still going up, but it's very modest compared to the previous run. So it
seems that something more than just opening and closing images has to be going
on.

Try again, this time open each image (same images), change colour depth to
8bit, then save as PNG in same folder.
At start-up of digikam:
%CPU    %MEM       VSZ      RSS TIME    COMMAND
37.4     4.1    1390416  168484 0:02    digikam
After 5 images:
%CPU    %MEM       VSZ      RSS TIME    COMMAND
41.1     6.2    1481260  252748 1:21    digikam
After 10 images:
%CPU    %MEM       VSZ      RSS TIME    COMMAND
39.9     6.4    1486236  259832 2:40    digikam
Looks like that's OK as well then.

So this bug only shows up if you do some amount of editing on the image it
seems. Will have to try doing more in the way of processing to work out when
the memory leaks start happening.

Idly wander if the preview images from the effects aren't being freed like they
should be? Or undo history stack? Colour depth conversion appears in the Undo
history but doesn't have a preview image because there are no parameters.

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