| Summary: | Crashed when attempting to vie images in folders | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Tom Coxon <fengshui> |
| Component: | Preview-Image | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | grave | CC: | anantapalani, caulier.gilles |
| Priority: | NOR | ||
| Version: | 2.9.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed In: | 3.3.0 | |
|
Description
Tom Coxon
2013-01-28 15:57:32 UTC
I've just tried to see if I can glean any more info. DigitKam seems fine when it's displaying a folder with jpg's, but when it gets a folder that includes PEF or DNG (from a Pentax camera) it crashes & not always via the KDE crash reporter. on my second go at this, KDE did catch it and reported Executable: digikam.exe PID: 2736 Signal: EXCEPTION_ACCESS_VIOLATION (0xc0000005) It also seems to have a problem with folders containing CR2 (Canon) files, but it's OK with TIFF's KDE reported this Executable: digikam.exe PID: 5624 Signal: EXCEPTION_ACCESS_VIOLATION (0xc0000005) Just tried it again and as soon as it got to the PEF file it crashed Executable: digikam.exe PID: 4852 Signal: EXCEPTION_ACCESS_VIOLATION (0xc0000005) I'm not sure if is is related, but I noticed that on a few jpg files it also displayed the "place holder" icon instead of the thumbnail of the image. and KDE gave this info for the back trace Application: digiKam (digikam.exe), signal: EXCEPTION_ACCESS_VIOLATION [unknown]!KiFastSystemCallRet() [[unknown] @ -1] at 0x7c90e514 [unknown]!WaitForSingleObject() [[unknown] @ -1] at 0x7c802542 [unknown]!QWaitCondition::wait() [[unknown] @ -1] at 0x6702855b [unknown]![unknown]() [[unknown] @ -1] at 0x60002 [unknown]![unknown]() [[unknown] @ -1] at 0x6eb79f8 [unknown]![unknown]() [[unknown] @ -1] at 0x7d08048 Having renamed the database & rebuilt it from scratch I got an abort with slightly different info Executable: digikam.exe PID: 4712 Signal: Unknown (0xe06d7363) (In reply to comment #5) > Having renamed the database & rebuilt it from scratch I got an abort with > slightly different info > Executable: digikam.exe PID: 4712 Signal: Unknown (0xe06d7363) Could you try the just release 3.1.0 and let me know if you still have problems? http://download.kde.org/stable/digikam/digiKam-installer-3.1.0-win32.exe Hi Ananta, I just installed the 3.1.0 windows (32 bit) version & repeated the steps which caused the crash in 2.9.0 & it works well. Just as I thought that it was completely fixed, it crashed on displaying a PEF (it was busy doing some I/O at the time). I restarted it, displayed the same image & it worked just fine. So it looks like there's probably a timing bug left somewhere which doesn't show very often. There are a few TIF's that it doesn't want to preview, but there are others that it's just fine with. But it doesn't crash with either. So it looks like it's fixed for practical purposes, but I'll exercise it some more over the net few days & let you know if I get any problems which can be reproduced. Kind regards, Tom Coxon On 10/06/2013 13:39, Ananta Palani wrote: > https://bugs.kde.org/show_bug.cgi?id=314033 > > Ananta Palani <anantapalani@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |anantapalani@gmail.com > > --- Comment #6 from Ananta Palani <anantapalani@gmail.com> --- > (In reply to comment #5) >> Having renamed the database & rebuilt it from scratch I got an abort with >> slightly different info >> Executable: digikam.exe PID: 4712 Signal: Unknown (0xe06d7363) > Could you try the just release 3.1.0 and let me know if you still have > problems? > > http://download.kde.org/stable/digikam/digiKam-installer-3.1.0-win32.exe > Thanks Tom for the feedback. Ananta plan also to release 3.2.0 for windows in near future... I close this file now. Reopen if necessary Gilles Caulier |