[Akonadi] [Bug 364005] ASSERT: "!mReadingFinished" when composing a message

Daniel Vrátil via KDE Bugzilla bugzilla_noreply at kde.org
Wed Jun 15 12:46:44 BST 2016


https://bugs.kde.org/show_bug.cgi?id=364005

Daniel Vrátil <dvratil at kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dvratil at kde.org

--- Comment #1 from Daniel Vrátil <dvratil at kde.org> ---
Yeah, this were a bugs we were trying to debug with dfaure - sometimes a job
was getting response that belonged to previous job which has ended, or has
signaled that it has ended and then another response arrived and the job
emitted another signal.

The assert helped us catch all the broken jobs and bugs in Job handling. The
last issue that triggers the assert is when a job is manually killed and the
session is restarted - which is exactly what happens in the completion code in
composer when you type fast enough so the composer kills the running
ContactSearchJob and starts a new one. I'm still trying to figure out how to
properly handle that, for now please just comment-out the Q_ASSERT.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Kdepim-bugs mailing list