[Xfce-bugs] [Bug 15730] New: high CPU usage when `Show flat buttons` is NOT selected in `Window Buttons` xfce4-panel plugin

[bugzilla-daemon at xfce.org]

https://bugzilla.xfce.org/show_bug.cgi?id=15730

            Bug ID: 15730
           Summary: high CPU usage when `Show flat buttons` is NOT
                    selected in `Window Buttons` xfce4-panel plugin
    Classification: Xfce Core
           Product: Xfce4-panel
           Version: 4.13.6
          Hardware: PC (x86_64)
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Medium
         Component: Window Buttons
          Assignee: xfce-bugs at xfce.org
          Reporter: howaboutsynergy at pm.me
  Target Milestone: Panel 4.14

In `Window Buttons` xfce4-panel plugin, in its settings there's `Show flat
buttons` option, if this is NOT selected, then the CPU usage(for both Xorg
process and xfce4-panel) is unusually high(say 25-39% for each, for 1 core of
CPU set to max 800Mhz) depending on how many buttons are currently present,
especially visible when painting of buttons happens such as when `Visual bell`
of xfce4-terminal is in effect and thus (at least) one button is blinking(too).
Or, when switching tasks by clicking on the window, even if the panel is hidden
(and thus the `Window buttons` are not visible) .

Selecting `Show flat buttons` reduces CPU usage for Xorg to about 7% (at worst)
on a CPU limited to 800Mhz seen via `top -d 2` (ie. 2 seconds refresh), and
about 5.9% CPU is the usual Xorg CPU usage. At best, no CPU usage difference is
detected between when a window blinks and when it doesn't.

tested
xfce4-panel 4.14pre2.r39.g5a497c25-1
commit 5a497c257fd9e035133fd9e89fc91079c9fb5fc8 (HEAD -> makepkg,
origin/master, origin/HEAD)
Date:   Thu Jul 18 06:30:45 2019 +0200

The only reason I was able to find this if because sometimes when
xfce4-terminal `Visual bell` is in effect and thus blinks the entire window
title, its respective button of `Window Buttons` does not blink(it should but
it doesn't sometimes) and thus no CPU usage increase is seen! This must be
another small bug, but thanks to it, I was able to track this one down!

-- 
You are receiving this mail because:
You are the assignee for the bug.