| Summary: | Crash while updating/generating fingerprints | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Torbjörn K. <torbjoern.k> |
| Component: | Searches-Similarity | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | caulier.gilles, torbjoern.k |
| Priority: | NOR | ||
| Version: | 2.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 2.0.0 | |
| Sentry Crash Report: | |||
| Attachments: |
valgrind backtrace of rebuilding fingerprints
GDB log of fingerprint crash new backtrace |
||
|
Description
Torbjörn K.
2011-06-29 13:02:05 UTC
*** This bug has been marked as a duplicate of bug 249248 *** Why does this crash still happen if it is solved? Did you fix it yesterday or today? If it is related to another library or package, can you tell me so, please? You are right. It's not a duplicate. Can you give us a valgrind backtrace ? Look in HACKING file for details. Gilles Caulier Created attachment 61470 [details] valgrind backtrace of rebuilding fingerprints I have to say, that I've never used valgrind before. Thus the attached results might be wrong. I worked with yesterdays master (last commit included: 055e495e9ec89806b1d2dd20b1ba9257a04d372d) and recompiled with CMAKE_BUILD_TYPE=Debug. Then I launched digikam with the valgrind command found in the HACKING file. In digikam I selected Tools->Rebuild Fingerprints. It run for several hours (~10k fingerprints had to be computed). Well, digikam did not crash. However, you might find the complete output useful. I stripped the output to be smaller than 1MB. '[...]' replaces several repetitions of the previous lines. The logs for configuration, make and install can be found on pastebun: http://pastebin.com/7dwWBxk8 (cmake) http://pastebin.com/FCqj3XbB (make) http://pastebin.com/0AvDdDvr (install) My assumption is, that this crash only occurs if the fingerprints are not available at all and have to be build the very first time. In addition, the crash I experienced above, occurred at about 50% of the process. digiKam 2.0.0 RC is out. Please check if crash is reproducible with this version. Thanks in advance Gilles Caulier Created attachment 61551 [details]
GDB log of fingerprint crash
Unfortunately it seems not fixed yet.
I compiled this morning from master (revision 5065db45) with BUILD_TYPE=RelWithDebInfo.
I manually backed up my SQLite DB and deleted it (together with the thumbnails-DB and the automatic DB backup files).
Then I launched digikam (from inside GDB) and thus forced it to reload all pictures and to create a new DB.
After having all pictures in the DB, I started building of all fingerprints. At the state of 47% it broke with the attached GDB log and backtrace.
After a relaunch of digikam, I started generation of the fingerprints again ("Rebuild All Fingerprints") and it crashed some per cent later: 52%. (see second GDB output in the attached file)
A third run made digikam crash at 40%. (I didn't attached that one)
Can you see which image crash digiKam ? look running backtrace in the console for details. Use kdebugdialog to enable right debug statements (digikam, libkexiv2, libkdcraw, libkface, etc...) Gilles Caulier Created attachment 61566 [details]
new backtrace
You are right, it is always crashing on the same image. However, a thumbnail of that picture can be created by digikam and it can be displayed without any problems.
I attached a new backtrace after launching digikam from the terminal. The debugging output is too big (4.8MB) to be attached here. Should I email it directly to you?
If image is smaller than 1Mb, attch it to this file. Else you can send me by mail or place it somewhere in internet to download Gilles Caulier I scanned your image on my computer and it do not crash for me... Gilles Caulier Same as #276999. If your thumbnails database is broken, this canbe the lead problem. Remove thumb DB file, and let's digiKam rebuilding it at the startup. Look if crash is reproducible. Gilles Caulier My broken thumbnails DB seems to be the cause of this bug. I deleted the digikam4.db and thumbnails DB, forced digikam to recreate both of them and selected the parent directory of the pictures, where it always crashed. Quitting digikam, restarting it and letting it create all thumbnails. Quitting it. And the finally building all fingerprints. It worked like charm. I close this bug. However, what might be the reason for a broken thumbnail DB? |