Re: [Evolution] [ews] Mark as read started being slow in 3.12.9 ( or 3.12.8 )

[Milan Crha <mcrha redhat com>]

On Wed, 2015-02-04 at 12:36 +0200, Robert Munteanu wrote:
> Hi,
>
> Using Evolution 3.12.9 on openSUSE 13.2 x86_64, KDE 4.14.4.
>
> I upgraded evo from 3.12.7 to 3.12.9 and I noticed that 'Mark as 
> read' started being quite slow. Typically I would select messages, 
> press Ctrl-K and move to the next one. Now Ctrl-K blocks the next 
> action and I have to wait until moving to the next message, which is 
> a
> flow-breaker for me. This does not happen for my IMAP account.
>
> I noticed using 'top' that when I do that evolution spikes the CPU 
> and it is in state 'D'. Is this a bug to report? Is there some way I 
> can work around it?

        Hi,
there doesn't seem to be anything directly related to a store of the 
read message state in evolution-ews changes between 3.12.7 and 3.12.9. 
Could you install debuginfo packages for evolution-data-server, 
evolution and evolution-ews and when you get to this state again, 
catch a backtrace of the running (currently probably stuck) evolution, 
which might show what it is trying to achieve, please? You can get the 
backtrace with command like this:
   $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt
Please check the bt.txt for any private information, like passwords, 
email address, server addresses,... I usually search for "pass" at 
least (quotes for clarity only).
        Bye,
        Milan