Bug 509332 - high gpu usage when panel using dodge windows/ auto hide mode
Summary: high gpu usage when panel using dodge windows/ auto hide mode
Status: RESOLVED DUPLICATE of bug 487895
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (other bugs)
Version First Reported In: 6.4.4
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-09 23:43 UTC by a
Modified: 2025-09-29 22:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description a 2025-09-09 23:43:40 UTC 
SUMMARY

high gpu usage when panel using dodge windows mode


STEPS TO REPRODUCE
1. enable dodge windows mode for tray panel
2. remove a widget on panel (such as digital clock)
3. maximize or full screen a window
4. if not reproduceable. logout, login, and repeat step 3

OBSERVED RESULT

100% gpu usage for plasmashell. move cursor to panel, make it appear will reduce gpu usage to around 0%. maximize or full screen a window will make gpu usage back to 100%

EXPECTED RESULT

plasmashell should not take whole gpu

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.10

ADDITIONAL INFORMATION
Comment 1 a 2025-09-10 04:37:27 UTC 
also reproduced in auto hide mode (not only dodge windows mode)
Comment 2 Nate Graham 2025-09-17 22:51:45 UTC 

*** This bug has been marked as a duplicate of bug 487895 ***
Comment 3 a 2025-09-29 22:21:43 UTC 
(In reply to Nate Graham from comment #2)
> 
> *** This bug has been marked as a duplicate of bug 487895 ***

https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/2565 is already merged to plasma 6.2. but i still having this issue on plasma 6.4. are you sure that they are the same bug?
Comment 4 Nate Graham 2025-09-29 22:29:02 UTC 
The merge request you found unfortunately didn't fully fix the issue, and we discovered that it's an upstream issue, not something we can fix ourselves.