https://bugs.kde.org/show_bug.cgi?id=321093
--- Comment #3 from Blackpaw <[email protected]> --- I realise this is of no interest to the developer but I added some extra logging to itemqueue.cpp to see what was happening: -------------------------------------------------------------------------------------------------------- bool ItemQueue::processBatch() { kDebug() << "pipline size: " << mItemPipeline.size() << mFetchedItemList.size(); if ( mRunningJobs > 0 ) {//wait until the old graph has been saved kDebug() << "blocked: " << mRunningJobs; return false; } if ( mRunningJobs != 0 ) { // added by me kDebug() << "mRunningJobs == " << mRunningJobs << "!!!!!"; } Q_ASSERT( mRunningJobs == 0 ); mRunningJobs = 0; -------------------------------------------------------------------------------------------------------- .xsession-errors akonadi_nepomuk_feeder(13953) ItemQueue::processBatch: mRunningJobs == -1 !!!!! ASSERT: "mRunningJobs == 0" in file /home/lindsay/Projects/akonadi/kdepim-runtime/agents/nepomukfeeder/itemqueue.cpp, line 116 -------------------------------------------------------------------------------------------------------- So for some reason mRunningJobs is actually -1, which I presume should never happen. How thread safe is this stuff? I don't see any use of thread sync primitives. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
