Seems to happen frequently when a lot of new files are created (e.g. extracting a kernel archive).
It is just spinning in g_main_loop_run, with a zero timeout on poll (see strace above). gdb backtrace:
#0 0x00007fb3c6e92e68 in ?? () from /usr/lib/libdbus-glib-1.so.2
#1 0x00007fb3c5e88a81 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#2 0x00007fb3c5e88ee8 in ?? () from /lib/libglib-2.0.so.0
#3 0x00007fb3c5e894bc in g_main_context_iteration ()
from /lib/libglib-2.0.so.0
#4 0x0000000000426899 in inotify_watch_func (source=<value optimized out>,
condition=<value optimized out>, data=<value optimized out>)
at inotify-monitor.c:93
#5 0x00007fb3c5e85492 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#6 0x00007fb3c5e89308 in ?? () from /lib/libglib-2.0.so.0
#7 0x00007fb3c5e8981d in g_main_loop_run () from /lib/libglib-2.0.so.0
#8 0x000000000041cb16 in main (argc=1, argv=0x7fffc2fc3848)
at tracker-main.c:1236
Seems to happen frequently when a lot of new files are created (e.g. extracting a kernel archive).
It is just spinning in g_main_loop_run, with a zero timeout on poll (see strace above). gdb backtrace: libdbus- glib-1. so.2 context_ prepare () from /lib/libglib- 2.0.so. 0 2.0.so. 0 context_ iteration () 2.0.so. 0 <value optimized out>, data=<value optimized out>) monitor. c:93 context_ dispatch () from /lib/libglib- 2.0.so. 0 2.0.so. 0 2.0.so. 0 3848)
#0 0x00007fb3c6e92e68 in ?? () from /usr/lib/
#1 0x00007fb3c5e88a81 in g_main_
#2 0x00007fb3c5e88ee8 in ?? () from /lib/libglib-
#3 0x00007fb3c5e894bc in g_main_
from /lib/libglib-
#4 0x0000000000426899 in inotify_watch_func (source=<value optimized out>,
condition=
at inotify-
#5 0x00007fb3c5e85492 in g_main_
#6 0x00007fb3c5e89308 in ?? () from /lib/libglib-
#7 0x00007fb3c5e8981d in g_main_loop_run () from /lib/libglib-
#8 0x000000000041cb16 in main (argc=1, argv=0x7fffc2fc
at tracker-main.c:1236