Bug 281492 - nepomukservicestub crashes on resume
Summary: nepomukservicestub crashes on resume
Status: RESOLVED DUPLICATE of bug 251795
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
: 258689 271599 280799 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-09-06 16:43 UTC by Rohan Garg
Modified: 2011-09-21 17:37 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rohan Garg 2011-09-06 16:43:34 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.7.41 (4.7.41 (KDE 4.8 >= 20110807)
Qt Version: 4.7.1
Operating System: Linux 3.0.0-10-generic x86_64
Distribution: Ubuntu oneiric (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
I had just brought the machine out of hibernation and the first things i notice are that nepomuk is hogging up 100 % CPU on multiple cores

- Unusual behavior I noticed:
nepomukservicestub seems to be hogging alot of CPU and crashes shortly after bringing a machine out of suspend

- Custom settings of the application:
None

The crash can be reproduced every time.

-- Backtrace:
Application: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fe04bc28780 (LWP 2034))]

Thread 3 (Thread 0x7fe03bc4b700 (LWP 2044)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fe04b59d933 in QWaitConditionPrivate::wait (this=0x1fb2820, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  0x00007fe04b59d6dd in QWaitCondition::wait (this=0x1fae828, mutex=0x1fae820, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x00007fe03c095d81 in Nepomuk::MetadataMover::run (this=0x1fae800) at /build/buildd/project-neon-kde-runtime-2+git20110904+r16959/nepomuk/services/filewatch/metadatamover.cpp:142
#4  0x00007fe04b59c3fe in QThreadPrivate::start (arg=0x1fae800) at thread/qthread_unix.cpp:285
#5  0x00007fe04b305edc in start_thread (arg=0x7fe03bc4b700) at pthread_create.c:304
#6  0x00007fe048be389d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fe03ac0e700 (LWP 2048)):
#0  0x00007fe048bd7773 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fe048027368 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe048027829 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe04b6f111c in QEventDispatcherGlib::processEvents (this=0x20065c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#4  0x00007fe04b6b6504 in QEventLoop::processEvents (this=0x7fe03ac0dd70, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fe04b6b6658 in QEventLoop::exec (this=0x7fe03ac0dd70, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007fe04b599c68 in QThread::exec (this=0x2005c50) at thread/qthread.cpp:490
#7  0x00007fe04b695a7b in QInotifyFileSystemWatcherEngine::run (this=0x2005c50) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fe04b59c3fe in QThreadPrivate::start (arg=0x2005c50) at thread/qthread_unix.cpp:285
#9  0x00007fe04b305edc in start_thread (arg=0x7fe03ac0e700) at pthread_create.c:304
#10 0x00007fe048be389d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fe04bc28780 (LWP 2034)):
[KCrash Handler]
#6  0x00007fe04b5962ba in QMutex::lock (this=0x1fb0158) at thread/qmutex.cpp:151
#7  0x00007fe04531add5 in QMutexLocker::QMutexLocker (this=0x7fff579b94d0, m=0x1fb0158) at /opt/project-neon/include/QtCore/qmutex.h:102
#8  0x00007fe045318044 in Soprano::Client::SocketHandler::~SocketHandler (this=0x1fb17a0, __in_chrg=<optimized out>) at /build/buildd/project-neon-soprano-2+git20110828+r1386/client/clientconnection.cpp:58
#9  0x00007fe045318108 in Soprano::Client::SocketHandler::~SocketHandler (this=0x1fb17a0, __in_chrg=<optimized out>) at /build/buildd/project-neon-soprano-2+git20110828+r1386/client/clientconnection.cpp:61
#10 0x00007fe04963af9c in QThreadStorage<QFontCache*>::deleteData (x=0x1fb17a0) at ../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:133
#11 0x00007fe04b59aa77 in QThreadStorageData::set (this=0x1db9a60, p=0x0) at thread/qthreadstorage.cpp:148
#12 0x00007fe04963b023 in qThreadStorage_setLocalData<QFontCache> (d=..., t=0x7fff579b95c0) at ../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:92
#13 0x00007fe049639d07 in QThreadStorage<QFontCache*>::setLocalData (this=0x1db9a60, t=0x0) at ../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:148
#14 0x00007fe0496378c1 in QFontCache::cleanup () at text/qfont.cpp:2632
#15 0x00007fe04972960f in QFont::cleanup () at text/qfont_x11.cpp:182
#16 0x00007fe049429b78 in qt_cleanup () at kernel/qapplication_x11.cpp:2624
#17 0x00007fe0493872bf in QApplication::~QApplication (this=0x7fff579b97c0, __in_chrg=<optimized out>) at kernel/qapplication.cpp:1163
#18 0x00007fe04a644701 in KApplication::~KApplication (this=0x7fff579b97c0, __in_chrg=<optimized out>) at /build/buildd/project-neon-kdelibs-2+git20110904+r92126/kdeui/kernel/kapplication.cpp:894
#19 0x000000000040459f in main (argc=2, argv=0x7fff579b9c78) at /build/buildd/project-neon-kde-runtime-2+git20110904+r16959/nepomuk/servicestub/main.cpp:102

This bug may be a duplicate of or related to bug 241600.

Possible duplicates by query: bug 241600.

Reported using DrKonqi
Comment 1 Sebastian Trueg 2011-09-21 17:35:31 UTC
*** Bug 280799 has been marked as a duplicate of this bug. ***
Comment 2 Sebastian Trueg 2011-09-21 17:35:58 UTC
*** Bug 271599 has been marked as a duplicate of this bug. ***
Comment 3 Sebastian Trueg 2011-09-21 17:36:23 UTC
*** Bug 258689 has been marked as a duplicate of this bug. ***
Comment 4 Sebastian Trueg 2011-09-21 17:37:03 UTC

*** This bug has been marked as a duplicate of bug 251795 ***