| Summary: | Digikam 3.4.0 crashes anytime face tags are used (manual or automatical naming, faces database re-building...) | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | olivier-jeannin |
| Component: | Database-Faces | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, msylwester |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 3.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.1.0 | |
| Sentry Crash Report: | |||
| Attachments: |
output of gdb
results with catch throw Sorry, here is it again, this time with throw catching and backtrace Another crash |
||
|
Description
olivier-jeannin
2014-01-22 10:44:50 UTC
The backtrace do not show any digiKam source code. Please run digiKam through GDB to get a better backtrace, as explained here : http://www.digikam.org/contrib Gilles Caulier Thanks a lot for your help. I tried to do as explained in the link you gave. First, using gdb : once in digikam, I tried the same as explain before. Digikam reacts the same, but this time never crashes (running progress stops at 2%, fan of the laptop starts to be noisy). It is to be noticed that only 2 images (3Mo) with no face in them are in the scanned folder... After a while, I quitted from the terminal (gdb asked my confirmation, as digikam was still running). Second, I tried exaclty the same using valgrind. Digikam did exactly the same, and stayed blocked at 2%. This time, I stopped gdb using Ctrl+C. In both cases, the terminal gave me hundreds or thousands of lines as results, that was lost... Should I try the same saving the results given by the terminal in text files ? >Should I try the same saving the results given by the terminal in text files ?
yes, only using GDB
Gilles Caulier
Here is the output. I did exactly the same in digikam, but once the process started, I switched to the terminal, then after a while I saw a new line with a cursor, and I wrote "bt", and then "quit" (you can see that in the text file. Many thanks Created attachment 84800 [details]
output of gdb
*** Bug 329108 has been marked as a duplicate of this bug. *** It's due to a C++ exception Gilles Caulier Is there anything I can do, or should I live with it ? I mean, I'm far from a developper myself, so is this C++ exception a know bug of digikam, or is it due to some wrong packages, settings, environnement I'm using ? In gdb, type "catch throw", then "run", provoke the crash. Now the backtrace will show the real location. Created attachment 84803 [details]
results with catch throw
You can find the output of gdb when I use catch throw in this attachment. Thank you for your help ! Comment on attachment 84803 [details]
results with catch throw
oh. At this point, you need to type "bt" to generate a backtrace.
Created attachment 84820 [details]
Sorry, here is it again, this time with throw catching and backtrace
Created attachment 84821 [details]
Another crash
In case this may help to find the issue, here is another crash, also with catch throw and backtrace. This crash happend during manual naming (manual rectangle drawing, and manual choice of person).
Comment on attachment 84821 [details]
Another crash
Is this the last released libkface or the current version from git? In the latter version, I would hope to have removed all usage of cv::FileStorage.
Please note there are not debug symbols for libkface available from your backtrace.
I have libkface-data 1.0~digikam3.4.0-1ubuntu3 and libkface2 1.0~digikam3.4.0-1ubuntu3 . How could I remove any usage of cv::FileStorage ? The coming 4.0 beta version will have the necessary changes OK, many thanks for your help. I will just wait for this version, trying not to forget any face name meanwhile ! Anyway, face tags are only one of the many functions of digikam, and I think this software is really good. Developpers do great job ! digiKam 4.0.0 is out : http://www.digikam.org/node/713 Please check if this entry still valid with this new version. Thanks in advance Gilles Caulier Hi, There are no more bugs with the 4.0.0 version, many thanks ! Best regards Olivier Jeannin |