Summary: | Revision 866710 (flicker fix) causes excessive CPU consumption | ||
---|---|---|---|
Product: | [Plasma] plasma4 | Reporter: | Kevin Kofler <kevin.kofler> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | aseigo, notmart, rdieter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Kevin Kofler
2008-10-10 22:14:33 UTC
this was fixed in trunk shortly after it was committed ... And the fix was? None of the patches which went into the file that patch touches after that revision appear to be addressing this. the fix was to not set the bitmap mask on each repaint. i believe it was Marco Martin who found and fixed the issue, we could probably ask him. <placeholder for the "this is why backporting unfinished work from trunk is a bad idea" speech> This one? http://websvn.kde.org/?view=rev&revision=866998 I didn't think that's related, but I must have been mistaken (as trunk doesn't eat CPU that way), I'll give that patch a try (also reenabling the anti-flicker patch which I disabled in the backport because of this issue). (I first didn't even find it because it was in a different file, and when I found it just a few hours ago, I thought that can't be it because it doesn't touch the same code. My mistake.) yep, that's the change =) Fixed (properly) in kdebase-workspace-4.1.2-6.fc10. (It was temporarily "fixed" in 4.1.2-5.fc10 by omitting the flicker fix. The 4.1.2-4.fc10 build with this bug was only in Rawhide for 1 day and never in F9.) Even 4.1.2-5.fc9 never even reached updates-testing, the plan is to push 4.1.2-6.fc9 there and see how it goes in testing. So don't panic, we aren't out there to break KDE. ;-) |