tracker-extract crashed with signal 31 in getrusage()

[Piotr Danecki]

None

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: tracker-extract 1.8.1-0ubuntu1~xenial2 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Dec 10 20:56:03 2016
ExecutablePath: /usr/lib/tracker/tracker-extract
InstallationDate: Installed on 2016-08-06 (125 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: /usr/lib/tracker/tracker-extract
ProcEnviron:
 LANGUAGE=pl_PL
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
Signal: 31
SourcePackage: tracker
StacktraceTop:
 getrusage () at ../sysdeps/unix/syscall-template.S:84
 ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30
 ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30
 ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30
 gnutls_global_init () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30
Title: tracker-extract crashed with signal 31 in getrusage()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Paraplegic Racehorse (paraplegic.racehorse)]

Just a note:

I routinely have to `kill -9` various tracker tasks because they each will use 100% of one of my CPU cores, which threatens to burn out my fan motor as things heat up. I have allowed the tasks to run for more than four hours, once, just to see if they would stop on their own. They do not.

tracker-miner and tracker-extract are the two worst offenders. I don't have any traces or logs from these kills, though, sorry.

It's so bad and so routine, I'm considering writing a shell script to find their PIDs and kill them easily with a single simple command.

[Adrian Ciriaci (ciriaci)]

Ok thanks for your comments My fan works automatically although
sometimes I have to turn it on.
Monitor system can view processes tracker-miner and tracker-extract and
kill them.
Although I do not think it's the problem. Excuse my bad english.

El 08/01/17 a las 01:40, Paraplegic Racehorse escribió:
> Just a note:
>
> I routinely have to `kill -9` various tracker tasks because they each
> will use 100% of one of my CPU cores, which threatens to burn out my fan
> motor as things heat up. I have allowed the tasks to run for more than
> four hours, once, just to see if they would stop on their own. They do
> not.
>
> tracker-miner and tracker-extract are the two worst offenders. I don't
> have any traces or logs from these kills, though, sorry.
>
> It's so bad and so routine, I'm considering writing a shell script to
> find their PIDs and kill them easily with a single simple command.

--