| Summary: | digikam crashes while scanning for faces | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | S. Burmeister <sven.burmeister> |
| Component: | Faces-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | althio.forum, caulier.gilles, fredericg_99, gaylord.doirat, i, kristian.hermann.karl, mail, obrienb8 |
| Priority: | NOR | ||
| Version: | 2.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 2.2.0 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
S. Burmeister
2011-07-15 01:02:44 UTC
Marcel, I think to have already seen this trace in another report, in the same condition. Right ? Gilles Caulier The bt is slighlty different, but I fear it's the same problem as infamous 269720 / 262596 *** Bug 279266 has been marked as a duplicate of this bug. *** *** Bug 279781 has been marked as a duplicate of this bug. *** Created attachment 63179 [details]
New crash information added by DrKonqi
digikam (2.1.0) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.3
- What I was doing when the application crashed:
I just selected one "unrecognized face", entered a name, and click on the button to validate the selection.
It happened several times, not necessarily when I validate a name : also when I click on the red cross ("this image is not a face")
-- Backtrace (Reduced):
#6 0x00000000005fdc4f in data (arole=37, this=0x36b9fa0) at /usr/include/QtCore/qabstractitemmodel.h:398
#7 Digikam::AssignNameOverlay::checkIndex (this=<optimized out>, index=...) at /raid/home/goulou/digikam/digikam-sc/core/digikam/items/assignnameoverlay.cpp:241
#8 0x00007f07ae30e76f in checkIndexOnEnter (index=..., this=0x1f8d6c0) at /raid/home/goulou/digikam/digikam-sc/core/libs/widgets/itemview/imagedelegateoverlay.cpp:282
#9 Digikam::AbstractWidgetDelegateOverlay::checkIndexOnEnter (this=0x1f8d6c0, index=...) at /raid/home/goulou/digikam/digikam-sc/core/libs/widgets/itemview/imagedelegateoverlay.cpp:270
#10 0x00007f07ae30e7d7 in Digikam::PersistentWidgetDelegateOverlay::slotEntered (this=0x1f8d6c0, index=...) at /raid/home/goulou/digikam/digikam-sc/core/libs/widgets/itemview/imagedelegateoverlay.cpp:577
Well, it seems that it happens every time I use "enter" to validate my choice. Digikam does not crash if I click on the "validate tag" button. Actually, I also saw that when I want to tag the photos, only half of those I selected get tagged : in this case, when I launch digikam after the crash, this is also true (half of my selected photos are tagged) *** Bug 280901 has been marked as a duplicate of this bug. *** *** Bug 280618 has been marked as a duplicate of this bug. *** Anyone here who can reliably reproduce this bug (mark something as a new face, tag, crash), is following current git and ready to apply some patches to collect debug info? (In reply to comment #9) Yes, I can. I have a repro that always provokes a crash. 1) After scanning of faces, 2) I select the "unknown"-tag folder, 3) I apply a filter (using tags) to narrow down the scope of faces, 4) Select a face and choose a people tag, 5) Select some more faces, 6) Then I click on the "ok" button which appears when one hovers over the picture 7) crash occurs If this is good enough, I'm more than willing to pull from current (which branch?) git and ready to apply some patches and to collect debug info. Created attachment 63499 [details] New crash information added by DrKonqi digikam (2.1.0) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.3 - What I was doing when the application crashed: I was selecting the entire amount of RAW images in the Faces tab that the facial recognition had detected and was attempting to remove the tag from them when digikam crashed. I have been able to re-produce the issue. I am curious if this has something to do with the other bug I have submitted https://bugs.kde.org/show_bug.cgi?id=279977 becuase I did notice a pattern that even though digikam crashed when selecting 100% of the 112 images when I re-started the application there were only 56 tags. So it seemed parallel to the other issue I had opened when selecting a range of images and only having half of them get untagged and then extraneous other images getting untagged as well. -- Backtrace (Reduced): #6 0x00007fc3486a69c7 in Digikam::ImageModel::imageInfo (this=0x0, row=0) at /home/ben/digikam-sc/core/libs/models/imagemodel.cpp:191 #7 0x00007fc3486a7003 in Digikam::ImageModel::retrieveImageInfo (index=...) at /home/ben/digikam-sc/core/libs/models/imagemodel.cpp:302 #8 0x0000000000602d70 in Digikam::DigikamImageView::removeFaces (this=0x154e280, indexes=...) at /home/ben/digikam-sc/core/digikam/items/digikamimageview.cpp:264 #9 0x0000000000601d59 in Digikam::DigikamImageView::qt_metacall (this=0x154e280, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0x7fffa3e51940) at /home/ben/digikam-sc/build/core/digikam/digikamimageview.moc:186 [...] #11 0x00000000006176c1 in Digikam::FaceRejectionOverlay::rejectFaces (this=0x15a1c20, _t1=...) at /home/ben/digikam-sc/build/core/digikam/facerejectionoverlay.moc:90 Git commit 16d8236edd31e57410caea49bf5e4dcc6b8fbda1 by Marcel Wiesweg. Committed on 10/09/2011 at 22:50. Pushed by mwiesweg into branch 'master'. Retrieve all information from the given indexes before starting to remove indexes Removing an index and then having invalid indexes may have introduced weird bugs. CCBUG: 277808 CCBUG: 279977 M +33 -15 digikam/items/digikamimageview.cpp http://commits.kde.org/digikam/16d8236edd31e57410caea49bf5e4dcc6b8fbda1 Git commit 59d37c11e55864bba8356d54e8f8739cbb3f0c4b by Marcel Wiesweg. Committed on 10/09/2011 at 22:37. Pushed by mwiesweg into branch 'master'. Add some more safety checks to avoid crashes in case of improper use (does not fix the reason of the crash, only the symptoms) CCBUG: 277808 M +17 -1 libs/models/imagemodel.cpp http://commits.kde.org/digikam/59d37c11e55864bba8356d54e8f8739cbb3f0c4b Kristian and obrienb8: can you try again with current git? If it still doesnt work, we'll need the mentioned round of debug patches. Created attachment 63556 [details]
New crash information added by DrKonqi
digikam (2.2.0) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.3
- What I was doing when the application crashed:
I was browsing one's person recognized faces, but several of them (6 in a row) were wrong : I selected those, clicked on the red cross (this is not a face). Digikam crashed immediately.
Note : There were 6 pictures that I wanted to untag. when I did it the first time, digikam crashed but the first 3 were actually removed as I can tell after restarting digikam. When I wanted to untag those 3, digikam crashed again (but it actually untagged 2 out of 3). The last time, I untagged the 6'th image indivually, and digikam didn't crash.
Digikam is from recent GIT (fetched yesterday, appears as 2.2.0 in the about box)
-- Backtrace (Reduced):
#6 size (this=) at /usr/include/QtCore/qlist.h:94
#7 size (this=) at /usr/include/QtCore/qlist.h:124
#8 Digikam::ImageModel::imageInfo (this=0x0, row=0) at /raid/home/goulou/digikam/digikam-sc/core/libs/models/imagemodel.cpp:191
#9 0x00007f320987946b in Digikam::ImageModel::retrieveImageInfo (index=<optimized out>) at /raid/home/goulou/digikam/digikam-sc/core/libs/models/imagemodel.cpp:302
#10 0x00000000005f29b8 in Digikam::DigikamImageView::removeFaces (this=0x252b730, indexes=<optimized out>) at /raid/home/goulou/digikam/digikam-sc/core/digikam/items/digikamimageview.cpp:263
You are sure to have included the two commits? The line numbers in the backtrace suggest you did not. Hi, No more creash with latest. I cloned latest fram master [1856bafe3262bc3594e16f2be65ed9d7eea09305], and built it using "cmake -DCMAKE_BUILD_TYPE=debugfull -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` .. " I then tried my repro that alwayes rendered a crash before, but no crash. That's cool :-) |