https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #19 from Bernd Steinhauser <li...@bernd-steinhauser.de> --- (In reply to Thomas Lübking from comment #18) > Doubleclick sounds like related to bug #357450 but should be resolved in > your KWin? I've never had this before updating to 5.5.95. But now that you point me to it, I'll try reverting it and see if it still occurs. Otherwise I'll open a bug. Guess we shouldn't discuss this here. > About the cross process CPU load I could imagine that this is due to a > swapping race in two GL contexts (your FF is gonna use HW acceleration, is > it? Check "about:config") resulting in an unclamped (otherwise afaiu QtQuick > only limits repaints by glSwapBuffer blocks) repaint cycle and insane FPS - > loading the CPU as much as possible. > > You should have better chances to trigger this with an OpenGL client > (glxgears or fancy GL hacks from xscreensaver) - but we're talking voodoo > here :-( Yes, glxgears get's laggy as well when triggering this. And that actually gave me an idea. Since I can trigger this with firefox as well (and the effect was strong), I tried before and after I killed plasmashell. As soon as plasmashell wasn't running anymore, everything was smooth as it should be. Before glxgears got very laggy as soon as I did just about anything in firefox. hw accel was enabled, but I tried the above before and right after starting plasmashell the effect is barely noticeable, so I will have to wait for a bit to report on that. -- You are receiving this mail because: You are watching all bug changes.
