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

[Richard Ash]

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





--- Comment #8 from Richard Ash <richard audacityteam org>  2010-01-06 22:45:32 ---
Sadly, the same symptoms can be produced with PNG files (compression setting 1,
for what it's worth). For all of the images I tested I did the same sequence of
operations:
1) Open Raw
2) White Balance
3) Sharpen
4) Aspect Ratio crop
5) Change Colour Depth to 8-bit
6) Save to PNG file (in a different album)

When I started digikam I ran free -m and it looked like this:
             total       used       free     shared    buffers     cached
Mem:          3962       2218       1743          0         97       1736
-/+ buffers/cache:        385       3577
Swap:        11719          2      11716
After processing 5 images it looked like this:
             total       used       free     shared    buffers     cached
Mem:          3962       3483        478          0         98       2321
-/+ buffers/cache:       1063       2898
Swap:        11719          2      11716
which might not matter (there is still free memory, and the cache has gone
up)), except that when I look at the process memory allocations by running ps
aux I get
%CPU    %MEM    VSZ     RSS     TIME    COMMAND
13.2    21.0    2062528 852468  2:35    digikam
0.0     0.1     148744  8040    0:00    kdeinit4:
0.0     0.1     147644  6908    0:00    kdeinit4:
0.0     0.6     319152  24860   0:00    kdeinit4:
0.0     0.6     320472  25604   0:00    kdeinit4:
0.0     0.7     322356  28464   0:00    kdeinit4:
0.0     0.0     7672    788     0:00    grep
so the main digikam process has slightly under 2GB of memory allocated.

If I carry on and do another 5 images in the same way, we get even more
allocated memory
%CPU    %MEM    VSZ     RSS     TIME    COMMAND
18.3    35.5    2641972 1443136 6:06    digikam
0.0     0.1     148744  8040    0:00    kdeinit4:
0.0     0.1     147644  6912    0:00    kdeinit4:
0.0     0.6     320936  25060   0:00    kdeinit4:
0.0     0.6     319248  24544   0:00    kdeinit4:
0.0     0.6     323008  26828   0:00    kdeinit4:
0.0     0.0     7672    804     0:00    grep
now 2.5GB allocated. Closing down the Image Editor window doesn't help must
with that:
%CPU    %MEM    VSZ     RSS     TIME    COMMAND
17.7    34.5    2599488 1400652 6:07    digikam
0.0     0.1     148744  8040    0:00    kdeinit4:
0.0     0.1     147644  6912    0:00    kdeinit4:
0.0     0.6     320936  25060   0:00    kdeinit4:
0.0     0.6     319248  24544   0:00    kdeinit4:
0.0     0.6     323008  26828   0:00    kdeinit4:
0.0     0.0     7672    808     0:00    grep

to get the memory back I have to quit digikam, as before. I'll try another
output format and no processing, see what that does to the results.

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