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

[Andrej Krutak]

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


Andrej Krutak <andree182 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andree182 at gmail.com




--- Comment #10 from Andrej Krutak <andree182 gmail com>  2009-09-26 22:15:46 ---
I'm experiencing this bug too - after editing like 10-20 images, digikam uses
1GB ram for no apparent reason... No idea yet, whether the source is the image
editor, or the digikam itself - however it made my computer freeze (for
out-of-memory reasons, obviously) a couple of times already, so it's quite
annoying...

After trying valgrind, the non-released memory was 13 MB - after doing some
common editing of 3 files.. This seems to not be the problem cause (as that
should be more like 50 MB or more).

Therefore, either I didn't reproduce the bug with valgrind being used (yet..
digikam is veeeery lazy when valgrinded), or the occupied memory is correctly
released when quitting digikam - but is purposelessly allocated after images
are closed. 

I hope I'll find the cause - it's pretty uncomfortable to close digikam after
every few edits... :)

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