https://bugs.kde.org/show_bug.cgi?id=363741
--- Comment #12 from Jan-Matthias Braun <jan_br...@gmx.net> --- Okay, I was able to remove a very reproducible crash (with the above mentioned segfault) during startup of akonadi (without any client running) by removing a search from the search folder in kmail. Since then, it is running for at least eight minutes (!) now and I haven't seen a SEGV up to now. By the way, is it normal, that different searches have the same name? In the logs I am seeing the Executing search "foo-1186278907-bar" lines. And the crashing search had the same name, as the search running before, which was much, much simpler. And checking now I see, that different searches often have the same search name in the logs, although from time to time the name seems to change. Revisiting older logs, the crash always happend with a reused search-name. But I cannot tell if it was the same search, always, because only now I went to instrument the code around the backtrace end in the akonadi-search code (xapian/xapiansearchstore.cpp:177) with lots of output. -- You are receiving this mail because: You are watching all bug changes.
