On Mon, 2007-07-30 at 11:21 +0200, Daniel Leidert wrote:
> Am Freitag, den 27.07.2007, 10:01 -0700 schrieb Ross Boylan:
> 
> > This problem significant affects usability and the performance of my
> > entire system.  It is new since the 2.10 upgrade.
> > 
> > When I'm using evolution, as often as every few minutes, it locks up
> > for awhile (10 seconds?) and becomes unresponsive.  It consumes all
> > available CPU.  I haven't noticed much of a pattern; I think it has
> > happend while scrolling the message list (which is long), while
> > scrolling a message in a compose window, and while typing a reply.
> > 
> > I am running under KDE.  My mailboxes are IMAP; some are quite large.
> > My INBOX is 20k messages.
> 
> I also observe this behaviour, mostly when walking through a very large
> IMAP folder, reading the mails. Then sometimes evolution becomes
> unresponsive for a few seconds. I cannot observe this every time.
> 
> I guess, I know what's maybe causing this: I prefer to get the mails
> every 5 minutes. As longer as evolution runs, it needs more and more
> time to fetch the mails - not because the count of mails it has to fetch
> increases. It simply gets more and more unresponsive when fetching the
> mails. Say in the first hour, it needs 1 second, when I press the button
> to fetch the mails. After running maybe 4 hours it becomes unresponsive
> for at least 10 seconds when I press the button to fetch the mails.
> 
> And maybe this process, that fetches the mails every 5 minutes, is
> causing the unresponsive times during walking through my folders too. I
> hope, you understand, what I want to say :) The issue is really a bit
> obscure.
> 
> @Ross: Maybe you observe the same? The next time the issue occurs for
> you, could you check, if the system also gets unresponsive, when you
> press the button to fetch the mails?
> 
> Regards, Daniel
> 
I've tried twice, and both times evolution does hang up after I hit
send/receive.  I've attached an strace.  The sequence was
1) start strace (of my existing evo session).
2) switch to evo window.  There was a several second pause during which
the panes were blank.  Eventually they were repainted.
3) hit send/receive.
4) wait for that to complete and for CPU use to go down.  Hit ^c on the
strace.

At this point evo has been running for c. 14 hours.


_______________________________________________
Pkg-evolution-maintainers mailing list
Pkg-evolution-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-evolution-maintainers

Reply via email to