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

[Richard Ash]

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





--- Comment #11 from Richard Ash <richard audacityteam org>  2010-01-09 22:07:46 ---
Created an attachment (id=39726)
 --> (http://bugs.kde.org/attachment.cgi?id=39726)
Output of valigrind in massig mode (for SVN r1072278 up to crash)

I tried this using a build from latest SVN (r1072278) because that has debug
symbols in it. I ran digikam from the top of the build tree (following the
instructions on http://www.digikam.org/drupal/download/KDE4, thanks!) as
valgrind --tool=massif ./digikam/digikam/digikam
but although I got the image editor open, as soon as I tried to open the White
Balance tool the whole lot crashed. I got two files, the one attached and an
identical file with the same mtime called massif.out.12961. I realise this
isn't what you wanted, so I'm backing up SVN to find a revision that doesn't
crash on white balance under Massif.

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