[Digikam-devel] [Bug 195448] New: random system hangs when handling RAW images in digikam

tony at beermad.org.uk tony at beermad.org.uk
Sat Jun 6 12:28:43 BST 2009


           Summary: random system hangs when handling RAW images in
           Product: digikam
           Version: 0.10.0
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel at kde.org
        ReportedBy: tony at beermad.org.uk

Version:           0.10.0 (using KDE 4.2.4)
OS:                Linux
Installed from:    Ubuntu Packages

Having discovered Digikam's excellent RAW-handling capabilities, I've been
using it intensively over the past couple of days re-editing my collection of
original files.

Unfortunately I'm being plagued by crashes at random times. Worse still, the
crashes take out my entire computer, leaving me with no alternative but to
reset it and reboot. I can't even SSH into the system to attempt a fix, though
the network card DOES respond to ping requests.

In case this was a problem with faulty memory, I left memtest running overnight
(more than 12 hours) and this found no problems at all.

The two common points at which this is occuring is during the RAW import
process (I'm using the RAW import tool) a couple of seconds after clicking the
"import" button, and when using the free-rotation tool. But I can't find a
pattern explaining what else triggers the crash; sometimes I can process a
dozen pictures and then it will crash. But then I can re-import the same file
with no problem.

I've installed Ubuntu's debug version of Digikam and tried running it with gdb,
but I'm  not seeing any useful information at the time of the crash; possibly
because the computer's hanging before it can print what gdb WOULD have told me?

I've also tried running Digikam with strace in the hope that this might provide
useful information, but I find that once the GUI has initialised, it seems to
detach itself from strace so I don't see any further information.

The result of the failure to get any useful debugging information means I'm not
giving you enough to fix the bug, so this is as much a plea for ideas of how I
might get more information about the crash; for example if it's possible to
prevent Digikam from detaching from strace.

...of course, how much information I'll be able to get will be limited by the
fact that there's no point in trying to write debugging information to a log as
the crash will prevent that from being written to disc so I can see it after
resetting the computer. But if I can capture as much as is still visible in a
terminal it MIGHT be useful.

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

More information about the Digikam-devel mailing list