Bug 1399874

Summary: tracker-miner-fs is consuming CPU power while on battery
Product: [Fedora] Fedora Reporter: Dominik Gronkiewicz <gronki>
Component: trackerAssignee: Igor Gnatenko <ignatenko>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: audrey, cgarnach, dakingun, debarshir, gronki, ignatenko, langdon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:09:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
output of gdb
none
Screen from top command none

Description Dominik Gronkiewicz 2016-11-30 00:25:35 UTC
Description of problem:
tracker-miner-fs is running 100% while on battery power which reduces battery life drastically. Killing the process helps to fix the issue temporarily.

Expected results:
tracker-miner-fs should not be indexing while on battery.

Comment 1 Debarshi Ray 2016-12-01 17:39:36 UTC
You can configure it using tracker-preferences.

Comment 2 Carlos Garnacho 2016-12-01 18:12:53 UTC
Tracker does slow down to processing 4 files per second while on battery, and even pauses entirely if on low battery.

If you are seeing 100% CPU use, it will have to be down to other reasons, in order to find out what those are, it'd be great if you provided a backtrace of the process at a time when you see it again using high cpu while on battery, in that case you can do:

$ gdb /usr/libexec/tracker-miner-fs `pidof tracker-miner-fs`

(gdb) t a a bt
...

And provide the output in this bug.

Comment 3 Dominik Gronkiewicz 2016-12-03 23:07:55 UTC
Created attachment 1227771 [details]
output of gdb

I am attaching the requested output.

Comment 4 Dominik Gronkiewicz 2016-12-03 23:09:39 UTC
Created attachment 1227772 [details]
Screen from top command

Comment 5 Fedora End Of Life 2017-11-16 19:16:47 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2017-12-12 10:09:09 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.