[Digikam-devel] [Bug 264363] New: image editor always crashes when triggering Colour Auto-Correction

[Adam Spiers]

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

           Summary: image editor always crashes when triggering Colour
                    Auto-Correction
           Product: digikam
           Version: 2.0.0
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: Image Editor
        AssignedTo: digikam-devel at kde.org
        ReportedBy: kde-bugs at adamspiers.org


Created an attachment (id=56449)
 --> (http://bugs.kde.org/attachment.cgi?id=56449)
capture of gdb session when digikam crashed

Version:           2.0.0 (using KDE 4.5.5) 
OS:                Linux

I compiled 2.0.0-beta1 on openSUSE 11.3 x86_64 like this:

mkdir build
cd build
cmake -DKFACE_EXTERNAL_FINDOPENCV:BOOL=TRUE -DCMAKE_BUILD_TYPE=debugfull
-DCMAKE_INSTALL_PREFIX=/opt/digikam2 ..
make
sudo make install

Then I ran it and tried to auto-correct the colour of an image:

1. /opt/digikam2/bin/digikam
2. Enter to select an image
3. F4 to enter image editor
4. Control+Shift+B to open Colour Auto-Correction

and it crashes every time.  Additionally, when drkonqi tries to get a
stacktrace, gdb crashes every time with a message like the following:

internal-error: virtual memory exhausted: can't allocate 11942884 bytes.

but I monitored with htop and there was still (a) physical RAM free, and (b)
2GB of swap completely unused.  So to work around this gdb bug, I re-ran:

gdb /opt/digikam2/bin/digikam

so that I could collect a partial stacktrace from gdb before gdb crashed.  The
results are attached.  I tried running both with and without
LD_LIBRARY_PATH=/opt/digikam2/lib64, and got the same stacktrace every time.

Reproducible: Always

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