| Summary: | Crash on adding GPS coordinates to multiple images. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Andrius <aegoreev> |
| Component: | Plugin-Generic-GeolocationEdit | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 6.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | 7.0.0 | |
| Sentry Crash Report: | |||
| Attachments: | logfile from DebugView | ||
Can you run digikam in the GDB and post the backtrace? Start the CMD.exe and execute the following commands: cd "C:\Program Files\digiKam" gdb digikam (gdb) r <=== "r" for run .... output from digikam...crash... (gdb) bt <=== "bt" for the backtrace (gdb) q <=== "q" for quit Maik Maik, Under Windows, we use now DrMinGW to get the crash backtrace automatically in a dialog in this kind of situation (as under Linux in fact). There is no specific reason to run digiKam in GDB as well. The DrMinGW crash handler must do the job instead. It's more simple for end users to report a dysfunction. Andrius, do you see the crash handler dialog appear when application crash ? If yes, all the relevant backtrace must be there. Just copy and paste the contents in this file. Look like Krita application use also DrMinGW. The team provide a nice documentation to get all debug information for developers : https://docs.krita.org/en/reference_manual/dr_minw_debugger.html Gilles Caulier Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just released ? https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/ (In reply to caulier.gilles from comment #2) > Maik, > > Under Windows, we use now DrMinGW to get the crash backtrace automatically > in a dialog in this kind of situation (as under Linux in fact). > > There is no specific reason to run digiKam in GDB as well. The DrMinGW crash > handler must do the job instead. It's more simple for end users to report a > dysfunction. > > Andrius, do you see the crash handler dialog appear when application crash ? > If yes, all the relevant backtrace must be there. Just copy and paste the > contents in this file. > > Look like Krita application use also DrMinGW. The team provide a nice > documentation to get all debug information for developers : > > https://docs.krita.org/en/reference_manual/dr_minw_debugger.html > > Gilles Caulier Gilles, no the application crashes quietly and there is no DrMinGW window pops up. (In reply to caulier.gilles from comment #3) > Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just > released ? > > https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/ I just added geolocation to about 500 images and the application did not crash... The only thing I have noticed is that digiKam regenerated thumbnails after I added GPS coordinates to the images. I am not sure why. Good news, After 2 weeks of works, the pre-release 6.1.0 bundles are now reconstructed from scratch with: - All OpenCV options for CUDA, OPenMP, and OPenCL disabled to prevent crashes in face management. - A large upgrade of Qt5 from 5.9.7 to 5.11.3. - An upgrade to KF5 5.55. - An upgrade to Ffmpeg 3.3.9 - The fontconfig/freetype integration in the bundle to reduce system dependencies Files can be downloaded here : https://files.kde.org/digikam/ Please test and report. Gilles Caulier Andrius ??? Ping. Please test with 7.0.0-beta2 pre-release from: https://files.kde.org/digikam/ We need a fresh feedback. Thanks in advance Gilles Caulier I did a large import to dk7b1 win64 around Christmas time and did not have any crashes. Perfect, thanks for the feedback Gilles Caulier |
Created attachment 116797 [details] logfile from DebugView digikam 6.0.0beta3 win_x64 just crashed on me three times in a row during applying GPS coordinates to multiple JPG+DNG images (more than 35 images). For your convenience I have attached a log from DebugView.