https://bugs.kde.org/show_bug.cgi?id=384372
--- Comment #14 from Heinrich Seebauer <heinrich.seeba...@swistec.de> --- (In reply to Michael Heidelbach from comment #13) If it's a file that utlimately causes the indexer's behaviour, shouldn't I expect it to occur again when I start indexing (i.e. call 'balooctl start')? In my case it did not run endlessly anymore after deleting the index. I would conclude that, having not changed anything in the setup or the indexed data sets, it might take more than a single file to provoke this behaviour. If the indexer runs amok again, I will compile me a debuggable version, and attach gdb to the running process. Maybe one could tell then where it's looping undefinitely. Thanks for your kind support Heinrich -- You are receiving this mail because: You are watching all bug changes.
