| Summary: | Crash during batch convert | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Joachim Johansson <joachim.j> |
| Component: | BatchQueueManager-RAWProcessing | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, richm+kde |
| Priority: | NOR | ||
| Version: | 2.1.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 2.4.0 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Joachim Johansson
2011-10-03 22:51:47 UTC
What about this bug report? Any news here? Joachim, could you please tell the exact steps you have taken? Or at least which tools you have used, to reproduce the crash. Andi digiKam 2.2.0 is out since few weeks. Crash still valid with this version ? Gilles Caulier Created attachment 65316 [details]
New crash information added by DrKonqi
digikam (2.2.0) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.2
- What I was doing when the application crashed:
I had a back queue (with 4 steps) running processing a number of files.
Then I went back to the main window and adjusted my filters to select some more images to process. Once selected I clicked the batch processing button on the top menubar and the crash occurred.
-- Backtrace (Reduced):
#7 0x08301f39 in setIcon (this=0xa5d72c0, icon=...) at /usr/include/qt4/QtGui/qtreewidget.h:230
#8 Digikam::AssignedListViewItem::setProgressIcon (this=0xa5d72c0, icon=...) at /build/buildd/digikam-2.2.0/core/utilities/queuemanager/views/assignedlist.cpp:107
#9 0x082f5f92 in Digikam::QueueMgrWindow::slotProgressTimerDone (this=0x9804fa8) at /build/buildd/digikam-2.2.0/core/utilities/queuemanager/main/queuemgrwindow.cpp:1008
#10 0x082fb97b in Digikam::QueueMgrWindow::qt_metacall (this=0x9804fa8, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbf9dce4c) at /build/buildd/digikam-2.2.0/obj-i686-linux-gnu/core/utilities/queuemanager/queuemgrwindow.moc:118
[...]
#13 0xb4bd72f7 in QTimer::timeout (this=0x9b67178) at .moc/release-shared/moc_qtimer.cpp:134
Created attachment 65317 [details]
New crash information added by DrKonqi
digikam (2.2.0) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.2
- What I was doing when the application crashed:
Same steps as before. Start a batch run on a number of images. Then select a different set of images from the main window thumbnail view. Once selected click the batch manager button and the crash happens.
-- Backtrace (Reduced):
#8 0x082f5f92 in Digikam::QueueMgrWindow::slotProgressTimerDone (this=0xa5e4dc8) at /build/buildd/digikam-2.2.0/core/utilities/queuemanager/main/queuemgrwindow.cpp:1008
#9 0x082fb97b in Digikam::QueueMgrWindow::qt_metacall (this=0xa5e4dc8, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfa81d1c) at /build/buildd/digikam-2.2.0/obj-i686-linux-gnu/core/utilities/queuemanager/queuemgrwindow.moc:118
[...]
#12 0xb4bb92f7 in QTimer::timeout (this=0xa8ff950) at .moc/release-shared/moc_qtimer.cpp:134
#13 0xb4b723ee in QTimer::timerEvent (this=0xa8ff950, e=0xbfa8223c) at kernel/qtimer.cpp:271
#14 0xb4b6b214 in QObject::event (this=0xa8ff950, e=0xbfa8223c) at kernel/qobject.cpp:1190
Richard: can you reproduce this every time? Is the first queue still busy while you start the next one? Gilles: it would seem that the d->currentTaskItem is invalid (deleted?) but not set to 0. Marcel, Yes, i see, and i fixed it for 2.3.0 : https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/42a2f8c95c6f27f1d28bdef310d1f95aad635f27 So, if people can try with digiKam 2.3.0, normally, it's already fixed. Gilles Caulier Created attachment 65873 [details]
New crash information added by DrKonqi
digikam (2.3.0) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.2
- What I was doing when the application crashed:
I just tried this with the philip5 natty ppa 2.3.0 packages and the problem still occurs.
To answer Marcel's questions:
I can reproduce it easily (it does seem to be every time). The other queue is still busy when I start the next one.
Just in case it helps to reproduce when I just tried I had 3 processing steps in my batch queue operation: auto level colours; remove meta data; apply metadata. I set the same for the 2nd batch queue entries.
-- Backtrace (Reduced):
#7 0x083032f9 in setIcon (this=0xa3af210, icon=...) at /usr/include/qt4/QtGui/qtreewidget.h:230
#8 Digikam::AssignedListViewItem::setProgressIcon (this=0xa3af210, icon=...) at /build/buildd/digikam-2.3.0/core/utilities/queuemanager/views/assignedlist.cpp:107
#9 0x082f72e2 in Digikam::QueueMgrWindow::slotProgressTimerDone (this=0x98d3fb8) at /build/buildd/digikam-2.3.0/core/utilities/queuemanager/main/queuemgrwindow.cpp:1017
#10 0x082fccdb in Digikam::QueueMgrWindow::qt_metacall (this=0x98d3fb8, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfb6e1cc) at /build/buildd/digikam-2.3.0/obj-i686-linux-gnu/core/utilities/queuemanager/queuemgrwindow.moc:118
[...]
#13 0xb4a682f7 in QTimer::timeout (this=0x99d14a0) at .moc/release-shared/moc_qtimer.cpp:134
Git commit 29ab1cb7a42cfb2145338eca30696ccd4077e351 by Gilles Caulier. Committed on 21/11/2011 at 13:36. Pushed by cgilles into branch 'master'. BQM : add new signal to dispatch busy state to AlbumGUI, to disable BQM action from GUI when it's busy. BQM cannot handle new item when processing is under progress, because it process all current queues as well. If new one is add in list, this can crash application. BUGS: 283281 M +1 -1 digikam/items/digikamimageview.cpp M +0 -5 digikam/items/imageviewutilities.cpp M +0 -1 digikam/items/imageviewutilities.h M +17 -6 digikam/main/digikamapp.cpp M +3 -1 digikam/main/digikamapp_p.h M +2 -0 utilities/queuemanager/main/queuemgrwindow.cpp M +1 -0 utilities/queuemanager/main/queuemgrwindow.h http://commits.kde.org/digikam/29ab1cb7a42cfb2145338eca30696ccd4077e351 |