On Tuesday 10 March 2009 14:30:57 Aaron J. Seigo wrote: > On Tuesday 10 March 2009, Artur Souza (MoRpHeUz) wrote: > > Hi guys, > > > > I'm in the middle of bossa conference so sorry for not providing a > > nice backtrace and debug information. > > I was using microblogging applet and sometimes my plasma was eating > > 100% of the cpu...after removing it from desktop, plasma started to > > behave well again and no "100% eating cpu situation" anymore. > > is this with Marco's "fix the layouting by moving to widgets" stuff in as > well? > > and what we really need is to determine whether it's the engine or the > widget.
A simple trick we often use for drivers is to simply attach the debugger to a process and stop it a few times. Out of 10 times around 9 will be around the exact spot where the bottleneck is (in this case it's even simpler because you can safely assume that if Plasma by default takes ~1% of time and the broken code ups that to 100% then percentage wise of stopping the debugger exactly where you want are at about 99% =) ). So attaching debugger when the usage jumps to 100% should very quickly give you an idea of what/where is going wrong. z _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
