Dave Howorth wrote:
On Tue, 5 Jan 2021 04:17:57 +0100 "Carlos E. R."
wrote: On 05/01/2021 02.00, David C. Rankin wrote:
On 1/4/21 1:04 PM, Carlos E. R. wrote:
No, it dies, and some control process starts it again (via systemd). Then it chokes and waits for some minutes, then starts again (search for <=== below)
It is probably trying to analyze files in my system that it can't. Same problem for years.
Oh..
Yep the log times show it. I see "Locale 'LANG' is not set, defaulting to C locale" -- I wonder if that figures into the issue. It says it's defaulting to C -- but how gracefully...
That's irrelevant... a red herring. I did not set the no locale thing, that was some default of the package itself. My session has a specific locale.
In any case, any wrong setting, any data set that can be input to a program, must not crash a program. A program has to allow for any kind of error on the input and cope with it gracefully. If a program segfaults, that's sloppy programming and never, ever, never the user fault.
tracker-extract has been crashing on this machine maybe for a decade, since it appeared. I report it, maybe they correct the problem, and then it goes crashing again on something else or on next upgrade.
If you google "tracker-extract" you will see reports going back for years.
I'm tired of reporting issues on it. So, does somebody really want the bugzilla?
On the man page, it says:
"The actual extraction is done by a separate process. This is done to isolate the calling process from any memory leaks or crashes in the libraries Tracker uses to extract metadata."
So it seems that maybe your problems are caused by some library you have installed that is borked or not compatible with tracker?
Maybe a poorly written library for some obscure/exotic file-format ? if you can think of any, might be worth omitting them from tracker. -- Per Jessen, Zürich (-0.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.