Bug 317071 - filewatch hogging one core gobbling RAM
Summary: filewatch hogging one core gobbling RAM
Status: RESOLVED FIXED
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: filewatch (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Nepomuk Bugs Coordination
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-20 11:32 UTC by Blackpaw
Modified: 2013-06-21 22:03 UTC (History)
3 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 Blackpaw 2013-03-20 11:32:01 UTC
Application: nepomukservicestub (0.1.0)
KDE Platform Version: 4.10.1
Qt Version: 4.8.4
Operating System: Linux 3.8.0-13-generic x86_64
Distribution: Ubuntu Raring Ringtail (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
Starting KDE. I had rebooted after building nepomuk core and akonadi/kdepim  from master.

I had two nepomukservicestub processes and one was using 100% of one core and was at 500MB+ of RAM and rapidly increasing. I killed it and got this crash report.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f11007df7c0 (LWP 2773))]

Thread 2 (Thread 0x7f10eeb17700 (LWP 2785)):
#0  0x00007f10fde0cb0d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f10fd47498f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f10fd435cbc in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f10fd4360f5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f10fd436284 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f11002d2026 in QEventDispatcherGlib::processEvents (this=0x7f10e00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007f11002a237f in QEventLoop::processEvents (this=this@entry=0x7f10eeb16d90, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f11002a2608 in QEventLoop::exec (this=0x7f10eeb16d90, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f11001a4410 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#9  0x00007f1100283ecf in QInotifyFileSystemWatcherEngine::run (this=0x1d2bb20) at io/qfilesystemwatcher_inotify.cpp:256
#10 0x00007f11001a6bec in QThreadPrivate::start (arg=0x1d2bb20) at thread/qthread_unix.cpp:338
#11 0x00007f10fdb0bf8e in start_thread (arg=0x7f10eeb17700) at pthread_create.c:311
#12 0x00007f10fde1ae1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f11007df7c0 (LWP 2773)):
[KCrash Handler]
#5  isSignalConnected (signal_index=2, this=0x0) at kernel/qobject_p.h:239
#6  QMetaObject::activate (sender=0x1d1ab40, m=<optimized out>, local_signal_index=0, argv=0x7fffc55b0ec0) at kernel/qobject.cpp:3448
#7  0x00007f10ef5357a2 in Nepomuk2::MetadataMover::movedWithoutData (this=this@entry=0x1d1ab40, _t1=...) at /home/lindsay/Projects/akonadi/nepomuk-core/build/services/filewatch/metadatamover.moc:123
#8  0x00007f10ef535dfd in Nepomuk2::MetadataMover::updateMetadata (this=this@entry=0x1d1ab40, from=..., to=...) at /home/lindsay/Projects/akonadi/nepomuk-core/services/filewatch/metadatamover.cpp:215
#9  0x00007f10ef5366d6 in Nepomuk2::MetadataMover::slotWorkUpdateQueue (this=0x1d1ab40) at /home/lindsay/Projects/akonadi/nepomuk-core/services/filewatch/metadatamover.cpp:128
#10 0x00007f11002b80df in QMetaObject::activate (sender=0x1aed9b0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3539
#11 0x00007f11002bd3dc in QObject::event (this=0x1aed9b0, e=<optimized out>) at kernel/qobject.cpp:1156
#12 0x00007f10fe5b78ec in QApplicationPrivate::notify_helper (this=this@entry=0x19ea720, receiver=receiver@entry=0x1aed9b0, e=e@entry=0x7fffc55b1850) at kernel/qapplication.cpp:4567
#13 0x00007f10fe5ba25b in QApplication::notify (this=0x7fffc55b1d30, receiver=0x1aed9b0, e=0x7fffc55b1850) at kernel/qapplication.cpp:4428
#14 0x00007f10ff5d5af6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#15 0x00007f11002a362e in QCoreApplication::notifyInternal (this=0x7fffc55b1d30, receiver=0x1aed9b0, event=0x7fffc55b1850) at kernel/qcoreapplication.cpp:946
#16 0x00007f11002d4b62 in sendEvent (event=0x7fffc55b1850, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#17 QTimerInfoList::activateTimers (this=0x19f0410) at kernel/qeventdispatcher_unix.cpp:622
#18 0x00007f11002d1994 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#19 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180
#20 0x00007f10fd435e85 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f10fd4361c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f10fd436284 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f11002d2006 in QEventDispatcherGlib::processEvents (this=0x19bbac0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#24 0x00007f10fe65d1ae in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x00007f11002a237f in QEventLoop::processEvents (this=this@entry=0x7fffc55b1ac0, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007f11002a2608 in QEventLoop::exec (this=0x7fffc55b1ac0, flags=...) at kernel/qeventloop.cpp:204
#27 0x00007f11002a7ce6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#28 0x00000000004040d4 in main (argc=2, argv=0x7fffc55b1ed8) at /home/lindsay/Projects/akonadi/nepomuk-core/servicestub/main.cpp:180

Reported using DrKonqi
Comment 1 Blackpaw 2013-03-20 11:40:02 UTC
Also the fileindexer was not running after this.
Comment 2 Vishesh Handa 2013-03-20 13:03:02 UTC
Oh!! So the filewatch service is gobbling up all the memory! I thought it was the storage service. Have you been moving a lot of files or something?
Comment 3 Blackpaw 2013-03-21 10:34:34 UTC
>Have you been moving a lot of files or something?

Afraid not. And the builds I've been doing are excluded from the watch list
Comment 4 Vishesh Handa 2013-03-21 12:19:22 UTC
Alright. Please run the file watch service under massif. 

$ qdbus org.kde.nepomuk.services.nepomukfilewatch /servicecontrol shutdown
$ valgrind --tool=massif nepomukservicestub "nepomukfilewatch"

I need to see what is consuming all the memory.
Comment 5 Vishesh Handa 2013-06-10 20:16:20 UTC
Ping?

Is this still gobbling a lot of your RAM?
Comment 6 Vishesh Handa 2013-06-21 19:14:30 UTC
Ping?
Comment 7 Blackpaw 2013-06-21 22:00:45 UTC
Yah, I think we can close this one - not an issue now for me.

Thanks.