Page MenuHomeSolus

Outdated Tracker causing high CPU load & overheating
Closed, InvalidPublic

Description

After a fresh Solus install my laptop was idling at 75C, which is about 25-30 degrees higher than it should be.

The culprit turned out to be tracker-extract process continuously trying to index files it could not deal with, like PDFs and epubs with non-UTF8 characters. I have since turned off tracker file indexing and the CPU and fan went back to normal.

This behaviour should fixed in the upstream (here and here). I don't know if tracker version is somehow fixed to the GNOME version, but the version currently in Solus seems particularly bad.

Event Timeline

satyrmode updated the task description. (Show Details)Feb 15 2019, 2:13 PM
satyrmode removed a project: Lacks Project.
Jacalz added a subscriber: Jacalz.Feb 15 2019, 2:34 PM

As a side note, since Budgie is not GNOME, maybe there is a way that Tracker could be dropped altogether or at least isolated from the rest of the DE so that it can be easily disabled? It seems like a fairly invasive program that I assume most people would not opt into if given the choice. It's indexing a lot of content and metadata for little pay-off (filename searching works perfectly fine without it), and when it's causing problems, it's not obvious as to how it should be disabled. Despite claims of efficiency, this kind of performance issue seems to be a recurring problem on the tracker-miners issues page (although, granted, most of them are getting solved).

Lorien added a subscriber: Lorien.Feb 15 2019, 5:49 PM

Not sure if it's related, but last week after I installed my new CPU cooler with a 4-pin fan (the old one had only 3 pins, so it was constantly spinning at 2k RPM) the RPM started fluctuating every couple of seconds, and I'm seeing tracker-extract periodically pop up in top. I just put in a low-noise adapter but the wavering is still noticeable.

Not sure if it's related, but last week after I installed my new CPU cooler with a 4-pin fan (the old one had only 3 pins, so it was constantly spinning at 2k RPM) the RPM started fluctuating every couple of seconds, and I'm seeing tracker-extract periodically pop up in top. I just put in a low-noise adapter but the wavering is still noticeable.

tracker daemon -t should terminate all tracker processes (for the current session, anyway). Does it help with your issue?

JoshStrobl closed this task as Invalid.Feb 15 2019, 11:38 PM
JoshStrobl added a subscriber: JoshStrobl.

Those issues will be resolved when we upgrade to a newer Tracker alongside the GNOME 3.30+ upgrade(s).

maybe there is a way that Tracker could be dropped altogether or at least isolated from the rest of the DE so that it can be easily disabled

We can't remove it (Nautilus compiles against it and a significant portion of Nautilus functionality nowadays requires it, like batch file renames).

tracker daemon -t should terminate all tracker processes (for the current session, anyway). Does it help with your issue?

Hard to tell but it seems fine now.

Matf added a subscriber: Matf.Feb 20 2019, 10:50 AM

I am having this issue since several months (probably around mid-2018) on a laptop that used to run acceptable temperatures with Solus. I am using tracker daemon -t since late 2018 as well every time I start a session, and can confirm it significantly reduces the CPU load and temperature, but this can only be a temporary workaround since it disables the tracker.

In T7604#144201, @Matf wrote:

I am having this issue since several months (probably around mid-2018) on a laptop that used to run acceptable temperatures with Solus. I am using tracker daemon -t since late 2018 as well every time I start a session, and can confirm it significantly reduces the CPU load and temperature, but this can only be a temporary workaround since it disables the tracker.

Just FYI, you can disable it more permanently by opening dconf editor, going to org.freedesktop.Tracker.Miner.Files and changing enable-monitors to False and crawling-interval to -2.

Matf added a comment.EditedJul 2 2019, 8:23 PM

I moved a folder containing small files into my /home partition and now my System is hanging because of tracker-extract chewing in my CPU. I hard to hard reboot because nothing was responsive, but the same happens when the system starts:

https://reho.st/0x0.st/z_tp.png

This screenshot was taken 90 minutes after booting and logging in my user session, CPU use has dropped to a low value, but it was initially 99%. There was nothing I could do but hard reboot and get the same issue again, or let the computer alone hoping it would be responsive later. Opening the terminal, tty console, glances, or taking a screenshot was impossible. The same happens when I reboot even though I left the tracker work for hours, I always have to eventually kill it to actually get my RAM back.

I used to run tracker daemon -t after boot if tracker-extract was taking too much CPU, but did so only occasionally when I noticed the strange CPU spikes discussed in this thread. What I observe now is very different, I don't even have the time to do so before the system hangs.

Is there something I can do?