GNOME Bugzilla – Bug 689167
tracker-extract eats 100% CPU if modules fail to load
Last modified: 2020-04-22 17:32:26 UTC
If tracker-extract fails to load its extractor modules, it enters an almost infinite loop, with 100% CPU and disk usage. Short strace extract: poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}], 2, 0) = 1 ([{fd=3, revents=POLLIN}]) read(3, "\10\0\0\0\0\0\0\0", 16) = 8 stat("/opt/gnome/lib64/tracker-0.14/extract-modules/libextract-text.so", 0x7ffff7fb3150) = -1 ENOENT (No such file or directory) stat("/opt/gnome/lib64/tracker-0.14/extract-modules/libextract-text.so.so", 0x7ffff7fb3150) = -1 ENOENT (No such file or directory) stat("/opt/gnome/lib64/tracker-0.14/extract-modules/libextract-text.so.la", 0x7ffff7fb3150) = -1 ENOENT (No such file or directory) open("/opt/gnome/lib64/tracker-0.14/extract-modules/libextract-text.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2652, ...}) = 0 write(10, "\n27 nov 2012, 15:30:37: Tracker-"..., 277) = 277 write(2, "\n(tracker-extract:3357): Tracker"..., 278) = 278 futex(0x13442a0, FUTEX_WAIT_PRIVATE, 2, NULL) = 0 write(9, "\1\0\0\0\0\0\0\0", 8) = 8 futex(0x13442a0, FUTEX_WAKE_PRIVATE, 1) = 0 This is repeated continuously, sometimes with this soname and sometimes with others. I don't know if this is the same file or another one. The /opt/gnome/lib64/tracker-0.14 folder is indeed empty, this is a jhbuild installation and modules are installed in tracker-0.15. Killing the extractor module did not help, it was respawned immediately. Also, for the first time I saw high CPU usage in the FS miner too, although that could be explained because I recently added one huge directory to index.
Hello, are you able to run : export TRACKER_VERBOSITY=3 : export G_MESSAGES_DEBUG=all : $prefix/libexec/tracker-extract -d -v 3 and provide the output please? It's hard to know what it's doing before it does this. Thanks.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!