It is 100% reproducible, i.e. it happens every single time I start indexing from scratch. I notice it after ~1 day or so. The other thing I'm sure of is that file-meta.db keeps on growing through the infinite loop. I've let it go on and on to see how long it keeps on doing it, and at one point the file-meta.db reached 1.3GB for a 15GB partition (from a size of 30MB when it originally was done indexing).
The growth rate seems approximately 60kB/second. What I'm still not sure about is what triggers it. What I do know is that once it gets stuck into that infinite loop, it keeps on repeating the infinite loop regardless of what I do (reboot, etc). The only thing that will stop it is an rm -rf ~/.cache/tracker. So your hypothesis that it's a corrupt db that's causing it seems plausible. It seems rather hard to catch it at the exact moment when it triggers but I have the following suspicions: 1) Could if have anything to do with ReiserFS? (I remember Beagle used to have some special mount requirements for reiserfs) 2) Could it be getting corrupted across a suspend/resume cycle? At one point I did suspend and resume just to see what would happen, but it stayed Idle. What I'll do now is do an rm -rf, then suspend/resume, and the reboot and see what happens. If I catch it triggering I'll be sure to report here. Hope I can find the problem, because I've come to rely on tracker and it's quite an excellent piece of software. -- Tracker continually reindexes same files, databases grow arbitrarily large https://bugs.launchpad.net/bugs/157523 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
