SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Load Digikam 2. Select "search" from far left hand side bar 3. Select "New Advanced Search" 4. Some where between clicking that and expanding the TAGs section the app crashs clean out. 5. Repeatable, every single time. 6. Including after a re-install of the software. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION Event View shows: Faulting application name: digikam.exe, version: 8.2.0.0, time stamp: 0x65673dbc Faulting module name: Qt6Core.dll, version: 6.6.0.0, time stamp: 0x6550a64d Exception code: 0xc0000005 Fault offset: 0x00000000002bcfb0 Faulting process id: 0x6158 Faulting application start time: 0x01da5d67c0a3aa00 Faulting application path: C:\Program Files\digiKam\digikam.exe Faulting module path: C:\Program Files\digiKam\Qt6Core.dll Report Id: 732bb4fd-0b77-4616-821b-8e3462cb473c Faulting package full name: Faulting package-relative application ID:
Fixed in 8.3.0. pre release. installer can be downloaded here : https://files.kde.org/digikam/
Thanks for the update. uninstalled 8.2, installed 8.3 Identical crash behaviour Event Log Faulting application name: digikam.exe, version: 8.3.0.0, time stamp: 0x65bf689f Faulting module name: Qt6Core.dll, version: 6.6.1.0, time stamp: 0x658eeb00 Exception code: 0xc0000005 Fault offset: 0x00000000002be3b0 Faulting process id: 0x5e6c Faulting application start time: 0x01da5d77855ae35b Faulting application path: C:\Program Files\digiKam\digikam.exe Faulting module path: C:\Program Files\digiKam\Qt6Core.dll Report Id: 6e212a21-1ddf-4aa5-8413-ae9c96aecf3c Faulting package full name: Faulting package-relative application ID:
Please capture the debugView trace as explained in this page : https://www.digikam.org/contribute/
Created attachment 165770 [details] digikam debug log file Installed debug version of 8.3.0 Went to Settings/Configure digiKam/Miscellaneous/System dialog page and turned on the option Enable internal debug logging to generate debug traces Ran DebugView and later digiKam, followed steps in bug report and this is the output
Installed 8.3.0 debug version Installed DebugView tool for windows attached debug output from steps listed in bug report. There is no digikam_crash.log in C:\Users\<my user name here>\AppData\Local\
The last file parsed sounds like this one : digikam.dimg: "P:/Photo_Albums/2014 ja October Bali/SANY5283.JPG" : "JPEG" file identified
The crash course under Windows has changed since 8.2.0. Now it require a debugger installed on the computer to catch the crash backtrace (the web page is a little bit outdated). A program as Microsoft Visual C++ or QtCreator must be installed to capture the dysfunction and to see where in code the problem appears. Best Gilles Caulier
Interesting. So I removed that one file "P:/Photo_Albums/2014 ja October Bali/SANY5283.JPG" And now (so far) no further crashes. Do you want a copy of that file to figure out why it is causing digikam to crash?
You have many broken images in your collection, such as this: digikam.dimg: Failed to read header of file "P:/Photo_Albums/2014 g July/IMG_20140712_141729.jpg" Can you provide the picture from Comment 6 or send it to me as a private email? Maik
(In reply to Maik Qualmann from comment #9) > You have many broken images in your collection, such as this: > > digikam.dimg: Failed to read header of file "P:/Photo_Albums/2014 g > July/IMG_20140712_141729.jpg" > > Can you provide the picture from Comment 6 or send it to me as a private > email? > > Maik Yes, so I noticed. mostly around 2014, clearly a bad sd card (or a number of them). digikam (without debug) quietly just handles them so I never really noticed. Now I have a new task to go through and clean up what I can when I get time. I'll add the photo as an attachment, there is nothing personal in it.
Created attachment 165771 [details] file that is crashing digikam here is the corrupted jpeg that is crashing digikam. enjoy!
The image does not cause digiKam to crash under Linux. With Windows I can reproduce it. Gilles, could it be that the exception handling in the DImg Jpeg Loader doesn't work under MSVC? We also had the problem with MinGW. Maik
yes i remember that. Bu i would expect that the problem only occurs with MinGW, not MSVC after all. Under VCPKG, the libjpeg version is : libjpeg-turbo | Version: 3.0.1 Star 3471 libjpeg-turbo is a JPEG image codec that uses SIMD instructions (MMX, SSE2, NEON, AltiVec) to accelerate baseline JPEG compression and decompression on x86, x86-64, ARM, and PowerPC systems. Compatibility:✓ arm-uwp ✓ arm64-windows ✓ x64-linux ✓ x64-osx ✓ x64-uwp ✓ x64-windows ✓ x64-windows-static ✓ x86-windows Gilles
This thread explain how to do it : https://stackoverflow.com/questions/19857766/error-handling-in-libjpeg The first part explain how to capture the error messages from libjpeg, that we already do i think. the second part explain how to catch exceptions. Gilles
The question is whether exception handling is enabled? https://learn.microsoft.com/en-us/cpp/build/reference/eh-exception-handling-model?view=msvc-170 Maik
If I understand correctly, there are exception handlers where the code is destroyed. But we want it to continue. Because with this Bug 480345, digiKam also terminates in the event of an exception, but should continue to run as under Linux. Maik
Hi, It's reproducible with last 8.4.0 release ? https://download.kde.org/stable/digikam/8.4.0/ Best Gilles Caulier
Hi, digiKam 8.5.0. is out with many fixes and improvements. https://www.digikam.org/news/2024-11-16-8.5.0_release_announcement/ This report still valid with this version? Thanks in advance Gilles Caulier
Hi, digiKam 8.6.0 is just released: https://www.digikam.org/news/2025-03-15-8.6.0_release_announcement/ Problem still exists with this version? Thanks in advance Gilles Caulier
This appears to be fixed in version 8.6.0 Following my own steps fails to reproduce the bug, digikam no longer crashes.