Comment 20 for bug 131983

I can confirm the behavior reported below by Jamie Lokier. Basically, Tracker seems to be done indexing (none of the permanent files grow by any amount), but it continues to write a temporary file to .cache/tracker and eat up 100% CPU.

3. The next it ran was after a power cycle. This time, for a couple of hours it stayed quite small (10M RSS), nice. But it was using 100% CPU, and hardly any I/O according to the Disk Usage monitor. A quick strace shows it doing repeated SQLite commits (and creating and unlinking a temporary log file with each commit). But crucially: it's doing this and no other system calls. This means it's doing a lot of commits, but not indexing anything. It's not reading my filesystem at all. Also, presumably it should never use 100% CPU for a sustained long time, if it's on the maximum throttle setting (which it is).