On Mittwoch, 27. April 2016 17:24:04 CEST Luca Beltrame wrote:
In data mercoledì 27 aprile 2016 17:18:41 CEST, Francesco Montesano ha scritto:
I get this also when akonadi is not sucking all the CPU
It's likely unrelated then. Installing debug symbols and providing a backtrace to the 100% CPU process would be helpful in finding the issue.
I had the same problem. backtrace attached. there are more than 80 threads, and it seems all but thread 34 are waiting in poll(). Thread 34 is in Akonadi::Server::Connection::readCommand()
But before that, does this also occur on a network loss?
no. Just with disconnecting or reconnecting the network it did not happen. -- Best regards/Schöne Grüße Martin A: Because it breaks the logical sequence of discussion Q: Why is top posting bad? () ascii ribbon campaign - against html e-mail /\ - against proprietary attachments Geschenkideen, Accessoires, Seifen, Kulinarisches: www.lillehus.at