No subject

that the processevent was managing a timeout event.
It seems that in the same moment I dropped the messages
(concluding the message movement action) a timeout expired
and the routine that manage the timeout hitted 
a variable with a wrong value, triggering the qt_assert at #11.

In my opinion that variable was modified by the routine
that move the messages, but the processevent stopped
that routine before its end; 
then processevent started the timeout management,
which found the wrong value in the variable and then asserted.

my 2 cents
Tom

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.