[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    [Bug 58908] composer slows down while editing and uses lots of cpu
From:       Eric Wilhelm <ewilhelm () sbcglobal ! net>
Date:       2004-07-03 1:03:57
Message-ID: 20040703010357.22316.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=58908      
ewilhelm sbcglobal net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|WORKSFORME                  |



------- Additional Comments From ewilhelm sbcglobal net  2004-07-03 03:03 -------
Okay, now I'm using 3.2.2 on debian 'sarge' and running kernel 2.6.6-1-k7-smp.

sorry:  "This backtrace appears to be useless.
This is probably because your packages are built in a way which prevents creating of \
proper backtraces, or the stack frame was seriously corrupted in the crash."

It does seem to be related to the checking of mail.  Also, if I run top, I only see \
XFree86 at the top of the cpu usage.  Jumping between words and backspacing seems to \
exaggerate it a lot.

I also forgot to mention previously that I was using Xinerama with three screens.  \
There is an nvidia geforce 4 (with the nvidia drivers) and a TNT2 card (using the nv \
driver.)  I don't see this on any other machines, so is it possibly related to \
xinerama?

It is difficult to reproduce, but it seems to follow this pattern:  start kmail, wait \
1.5 minutes (mail scheduled to check every 2 min), then start a new message and type \
at full speed (~ 40-50 wpm for me.)  When the main kmail window starts the "Preparing \
transmission" message, the slowdown starts then.  It's a lot like word-processing on \
a 386 (except this is an AMD 2200 MP.)

If I use an external editor (even kwrite) there is no trouble.
_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel


[prev in list] [next in list] [prev in thread] [next in thread]