[bug][1.1.9.28] tracker-miner-fs stuck in a loop
The tracker-miner-fs appears to be stuck in a loop:
- has been running for hours
- consumes 50% of system RAM
- has high CPU usage
- the device is quite hot and the UI is unresponsive
journal is flooded of:
Sep 11 10:30:40 Jolla tracker-miner-fs[1361]: GLIB CRITICAL ** Tracker - Could not execute sparql: GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: UNIQUE constraint failed: nie:DataObject.nie:url (strerror of errno (not necessarily related): Resource temporarily unavailable)
So it kinda looks like its database died or is otherwise unavailable but it still tries to connect to it again and again.
Was about to file a report here, because I'm hit by this, too. Reboot doesn't help, killing tacker doesn't help. After 3 hours uptime the battery is only 54%.
Btw, it only started today or yesterday evening, before it all worked normally. Yesterday evening I started to let FlowPlayer index files and download covers. Possible connection of these two?
This is a real showstopper, as I can't take my Jolla with me for more than a half day :(
dalas.revo ( 2015-09-11 12:09:31 +0200 )edit@dalas.revo: Reboot seems to have worked in my case, at least a bit - tracker is still running after reboot, still consumes 100% CPU (50% miner, 50% store) but does not use all the memory as before and does not flood the log with the Resource temporarily unavailable messages. But it could be that it will only get stuck later.
MartinK ( 2015-09-11 13:11:35 +0200 )editDo you also have FlowPlayer? Does it interfere with tracker in any way?
dalas.revo ( 2015-09-11 13:14:10 +0200 )edit@dalas.revo: I also have it but I don't think I have started it recently ad it IIRC does not have any daemon component.
As for whats happening now:
Still, this is something I would expect to happen on AC power, not when running from battery. I think the only reason my Jolla has not run out of battery due to maxed-out CPU just yet is the hard suspend Jolla does when the screen is off. Otherwise I'm pretty sure the battery would be empty. I would kinda think tracker would be more constrained for on-battery operation.
Another think I have noticed - tracker-miner-fs has a nice of 19 while tracker-store has the default value (0). This is kinda weird as due to the similarly high memory usage they appear to be basically feeding each other, so different nice value looks weird.
MartinK ( 2015-09-12 01:41:05 +0200 )editSorry for not answering for so long, had visitors over the weekend. I didn't think about a daemon but more about a corrupted database, but I do know too little about the way tracker works. Anyway, what I am experiencing now is this: My device is nearly unusable, because
If till this evening no one from Jolla steps in and helps or I don't find any other way to stop this, I have to reset my device :( I need it and can't charge it every 5 hours.
dalas.revo ( 2015-09-14 10:22:22 +0200 )edit