Same family of failure, but on a much larger corpus and with a worse
outcome - filed separately as LP: #2173614.
On localsearch 3.11.0-1ubuntu1.1 (resolute) with ~25,000 scanned PDFs in
$HOME: the extractor is killed on a new file every 7-8 seconds ("File
'...' took too long to process. Shutting down everything" / "Extractor
subprocess died unexpectedly"), localsearch-3 sits at 6.5 GiB RSS
burning a full core, none of the PDFs get indexed (23,323 entries under
~/.cache/tracker3/files/errors/), and meta.db is flagged as corrupted
twice - first the .localsearch.corrupted marker on the old DB, then
"database disk image is malformed" on the freshly rebuilt one. The miner
also crashed once with "free(): invalid next size (normal)" (SIGABRT,
core kept).
So in addition to the log flood and the CPU loop, the per-file deadline
path can leave the index database unusable. #2173614 carries the full
journal evidence, the poppler timings of the offending files, and the
workaround I applied (ignoring *.pdf / *.epub), plus a note that
resolute-proposed has 3.11.2-0ubuntu0.1 if testing it from -proposed
would help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110914
Title:
localsearch-extractor-3 gets stuck and fills syslog
To manage notifications about this bug go to:
https://bugs.launchpad.net/tracker/+bug/2110914/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
