Revision 68dde51...

Go back to digest for 2nd September 2012

Bug Fixes in KDE Base

Vishesh Handa committed changes in [nepomuk-core/KDE/4.9] services/fileindexer/indexscheduler.cpp:

FileIndexer: Fix a deadlock by making the mutex recursive

The following deadlock occurs during the first run of the
nepomuk-fileindexer, if you're on batery

QMutex::lockInternal()
QMutexLocker::QMutexLocker
Nepomuk2::IndexScheduler::suspend
Nepomuk2::EventMonitor::pauseIndexing
QMetaObject::activate(QObject*, QMetaObject
Nepomuk2::IndexScheduler::indexingSuspended
Nepomuk2::IndexScheduler::suspend
Nepomuk2::EventMonitor::pauseIndexing
Nepomuk2::EventMonitor::slotPowerManagementStatusChanged
Nepomuk2::EventMonitor::EventMonitor
Nepomuk2::FileIndexer::FileIndexer

This only happens during first run cause that is when the EventMonitor
is connected to the IndexScheduler


REVIEW: 106230

File Changes

Modified 1 files
  • services/fileindexer/indexscheduler.cpp
1 files changed in total