From kde-optimize  Tue Mar 23 16:32:23 2004
From: Andras Mantia <amantia () freemail ! hu>
Date: Tue, 23 Mar 2004 16:32:23 +0000
To: kde-optimize
Subject: 100% CPU usage in Quanta
Message-Id: <200403231832.23371.amantia () freemail ! hu>
X-MARC-Message: https://marc.info/?l=kde-optimize&m=108005958805163

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

 I don't know if this or the core devel list is better, but let's try. I found
that since I've rebuild my whole KDE system, Quanta is using ~100% of the
CPU. The system is not noticeable slower, so it was not even easy for me to
detect this change, I just saw my CPU temperature going up constantly. First
I thought that yes, it's a Quanta problem. I've tried to interrupt the
running Quanta and look at the backtrace. It never showed a Quanta call, but
there was always some QTimer::singleShot call in the log. So I've put
breakpoints to all such calls in Quanta and enabled heavy debugging
information, but... the breakpoints were not reached, the debug showed that
the methods which are called by singleShot timer in Quanta are not called,
yet it still uses ~100% of CPU. :-(
 Now I've compiled the same Quanta sources on a KDE 3.2.1/ Qt 3.3.1 (SuSE
RPM's) and no problem, there is no such high CPU usage. So the problem lies
in qt-copy or kdelibs CVS HEAD. But I'm stuck here, and don't know how to
find the real cause. Any idea how to start? I've tried cachegrind, but it's
too strange for me... I've tried valgrind --tool=cachegrind quanta_be and
loaded the generated log to kcachegrind, but I don't know how to continue.

Andras

- --
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAYGaXTQdfac6L/08RAuc0AJkBPVDYqAiQWRTYdFFwJmnC6ZBBNACg0f9o
bqMykn0hasu0Wf9uBBux0+o=
=Pe71
-----END PGP SIGNATURE-----
_______________________________________________
Kde-optimize mailing list
Kde-optimize@kde.org
https://mail.kde.org/mailman/listinfo/kde-optimize