tracker-miner-fs crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tracker-miners (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Tracker processes using up >90% of the processor too often. Unplugging laptop from power causes processes to crash. Something needs to be done to keep tracker from running my machine hot all the time, else I will be forced to remove it.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: tracker-miner-fs 2.0.2-1
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 18 08:39:44 2017
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2016-12-03 (318 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fd7fa91a046: mov 0x18(%rdi),%rbp
PC (0x7fd7fa91a046) ok
source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tracker-miners
StacktraceTop:
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
Title: tracker-miner-fs crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-09-28 (19 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| Christopher M. Rogers (cajhne) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1713629, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.