https://bugs.kde.org/show_bug.cgi?id=378010
--- Comment #11 from David Edmundson <k...@davidedmundson.co.uk> ---
Recompiling is the quickest way.
You could do probably do it with GDB skills, but frankly it's not worth it
especially as we don't want to interrupt the processing as that could skew
results.
if you're on Debian/Ubuntu
apt-get build whateverPackageKWindowSystemIsIn
apt-get source whateverPackageKWindowSystemIsIn
make the changes
fakeroot debian/rules binary
sudo dpkg -i ../*.deb
as for the debug in kwindowsystem.cpp
under if (dirtyProperties || dirtyProperties2) {
add
qDebug() << "DAVE " << eventWindow << dirtyProperties << dirtyProperties2;
For other distros check out their own guides, if you can't figure it out, let
me know what you're on and I'll get someone from that distro to help.
Get debug by running plasmashell from a konsole, you're also going to then have
to turn the window ID into something useful by running "xprop -id
SOMENUMBERHERE"
As for the remaining CPU, it's a bit hard to interpret something. Not
everything is very readable, especially when you have an event queue.
The biggest issue is it's quite easy to fall into traps like micro-optimising a
method that gets called a lot rather than figuring out why it gets called a
lot, which is why I can't just read a log and do something about it, it
requires deeper investigation.
Also, thanks in advance.
--
You are receiving this mail because:
You are watching all bug changes.
