This is actually a very old issue (https://esite.ch/2012/04/saving-power-with-diodon-0-8-0/) when using primary selection clipboard GTK didn't trigger owner-change signal https://developer.gnome.org/gtk3/stable/gtk3-Clipboards.html#GtkClipboard-owner-change
A workaround to this was to run a timer which periodically checks the primary selection clipboard. That's why you see the high CPU utilisation.
As this has been a while back I have now tested it again and it actually seems to work now with newer GTK versions without the timer.
A patch is in the making https://github.com/diodon-dev/diodon/pull/22
This is actually a very old issue (https:/ /esite. ch/2012/ 04/saving- power-with- diodon- 0-8-0/) when using primary selection clipboard GTK didn't trigger owner-change signal https:/ /developer. gnome.org/ gtk3/stable/ gtk3-Clipboards .html#GtkClipbo ard-owner- change
A workaround to this was to run a timer which periodically checks the primary selection clipboard. That's why you see the high CPU utilisation.
As this has been a while back I have now tested it again and it actually seems to work now with newer GTK versions without the timer.
A patch is in the making https:/ /github. com/diodon- dev/diodon/ pull/22