Summary: | digiKam crashes when launching scan and recognize faces | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Žygimantas Bruzgys <un1x0nly> |
Component: | Faces-Detection | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | arojas, caulier.gilles, mario.frank |
Priority: | NOR | ||
Version: | 5.8.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | 6ea9e4289a88c167526d7cb6fdadadbbfc83e0b8 | Version Fixed In: | 5.9.0 |
Description
Žygimantas Bruzgys
2018-02-09 09:57:45 UTC
Can you reproduce the crash using the Linux AppImage 5.9.0 instead your system package ? https://files.kde.org/digikam/ Gilles Caulier I've downloaded 5.8 appimage and it already seems that I cannot reproduce the same problem. :/ It crashed once, but I was not able to get the BT. Then I've restarted it and from then on it worked fine. So i suspect that OpenCV from you computer is compiled with all options enabled, and especially the famous Intel thread support. OpenCV is a big puzzle. For the digiKam AppImage bundle i disable all and let's only the core of library. After all we use only a small part of the library here. AppImage bundle use also openCV 3.4. About others crash, where these happen ? What's the trace on the console ? What's the GDB trace using "debug" CLI option from the bundle ? Gilles Caulier Unfortunately, when it crashed I was not able to get the BT. And it seems that it was a transient crash, since after a restart it worked fine. I think that in order to reproduce this crash I would need to clear my faces DB, which I would not want to do right now. As this seems to be dependent on an external dependency, which seems to be configured correctly in a release image, I'll mark the bug as resolved. (In reply to Žygimantas Bruzgys from comment #4) > Unfortunately, when it crashed I was not able to get the BT. And it seems > that it was a transient crash, since after a restart it worked fine. I think > that in order to reproduce this crash I would need to clear my faces DB, > which I would not want to do right now. > > As this seems to be dependent on an external dependency, which seems to be > configured correctly in a release image, I'll mark the bug as resolved. Hey Žygimantas, if you have a SQLite DB, you can just copy your current faces DB file to some safe place so you have a backup. Then you can delete the original face DB file and digiKam will automatically generate the empty faces DB. Then you could probably get a stack trace. In case any other packager stumbles upon this, it's fixed by 6ea9e4289a88c167526d7cb6fdadadbbfc83e0b8 |