Hi, I use KMail2 version 4.10.5. I've choosed the SQLite backend during the migration from KMail1 to KMail2. Now KMail2 randomly hangs. Regards, Carsten Reproducible: Sometimes Steps to Reproduce: It occurs often and randomly. Thereby I can't provide steps to reproduce. Actual Results: The Akonadi Console show jobs inside "job tracker" with state "Running" or "Initial" and the states haven't changed since hours sometimes. The Debugger inside the Akonadi Console shows some odd job details: 1) The panel "akonadi_mixedmaildir_resource_0 (0x9e55ea0)" show a started job "13763 BEGIN" but the state of the job hasn't changed last 20 minutes. 2) The panel "KMail Kernel ETM (0x9eaf090)" has an open fetch job 993 UID FETCH 34917 EXTERNALPAYLOAD (UID REMOTEID REMOTEREVISION COLLECTIONID FLAGS SIZE DATETIME PLD:ENVELOPE) * 34917 FETCH (UID 34917 REV 95 REMOTEID "9875772" MIMETYPE "message/rfc822" COLLECTIONID 636 SIZE 5268 DATETIME "11-Oct-2013 15:35:56 +0000" FLAGS but no "OK UID FETCH complete". 3) The panel "kmail2-851671093 (0x9dee108)" show an open job 237 UID STORE 63309 NOREV (REMOTEID "44023286" +FLAGS (\SEEN)) but no "OK UID STORE complete". I won't attach the log because it contains sensitive email information.
Created attachment 82933 [details] Backtrace of akonadiserver created using gdb "bt full" at 2013-10-16
Created attachment 82934 [details] Backtrace of akonadiserver created using gdb "bt full" at 2013-10-18
Today I've added to files with the output of gdb "bt full" attached to the process "akonadiserver". The output created at 2013-10-16 shows a normal situation and the output created at 2013-10-18 shows the hanging situation. The second situation hasn't changed after 30 minutes. Looks like the output from 2013-10-18 shows a classical dead lock situation. It looks like a big locking bug in your code. Regards, Carsten
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.