Summary: | Crash on adding things to batch queue | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Nathan <nathan> |
Component: | BatchQueueManager-Workflow | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 1.2.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.5.0 | |
Sentry Crash Report: |
Description
Nathan
2010-09-23 14:21:04 UTC
Not reproducible here. Try with digiKam 1.4.0 Gilles Caulier I can confirm this! Add images to the first queue (CTRL+B), use a filter, start the processing. Now select other images while the BQM is running, and add them to a second queue (SHIFT+CTRL+B) => BOOM! I guess the problem has something to do with the fact that no tool is assigned to the second queue... When you just add items to queue1 and items to queue2, assign a tool to queue1 (not queue2) and press "Run", you get a warning message (you have not assigned a tool to queue2). Maybe this is the reason? BQM is already running, a second queue is added, no tools are assigned and BQM accesses a nullpointer (or something like this, I couldn't figure out the reason for the crash yet). Hum. If BQM is buzy, it will be better to disable options to add new items. Because BQM process all queue set in the pool, if you add a new queue when it run, there is no test to limit queue processing to the queue list set when user start it. Gilles SVN commit 1182409 by cgilles: if BQM is busy, disable action menu to add new items to current or new queue. This is a temprally fix, until the queue manager will use open mp and run queue to process in parallele. BUGS: 252130 M +5 -3 contextmenuhelper.cpp M +2 -2 contextmenuhelper.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1182409 |