https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #35 from tagwer...@innerjoin.org --- (In reply to Peter Wibberley from comment #34) > No idea what to make of all this! I would try a fresh install, but I had > hoped the switch to the User Edition would achieve the same thing. Any > suggestions? Feels like a handful of random jigsaw puzzle pieces :-) I think you are now OK with the "max_user_watches". The baloo_file process is picking up all your directories and able to watch for changes. I'm not sure what to make of the dump, can always hope that someone else jumps in to help. It could be that you'll get a "you need to install the debug symbols". The "??"s in the dump would then appear as function names / line numbers Some speculation though... It looks as if the crash happens when updating the index, not when reading any particular file; "liblmdb" is the library that accesses the index. It also looks as if baloo is trying to delete a "load" of index entries. This fits with your "Checking for state index entries" in Comment 11. And early on you said your index file was 28 GB, which is, well, a lot. You can get a breakdown of how much free space in the database with "baloo indexSize". I wonder though whether the next step is to disable baloo, rename the baloo "index" file so it is out of harms way, and reenable to start the indexing process again. It could take a while... Maybe you can "phase" the reindexing, starting with a few folders, checking the behaviour, and then adding more -- You are receiving this mail because: You are watching all bug changes.
