Open HoodedDeath opened 3 years ago
Have now confirmed Deckmaster's high CPU usage starts when logging out and logging back in. Xorg read error potentially caused by a bug Opera is having on my system where every Opera window fights for focus as fast as possible. This may be causing some pilling up in Deckmaster's window-change queue
Having the exact same problem. It was using 200+% according to htop.
And I do not use Opera, so that's not the issue, at least not for me. Restarting the deck solves the problem. I'm going to run Deckmaster through the terminal for a bit and see if it eventually spits out anything interesting.
Unfortunately, it looks like Deckmater is abandoned, which is disappointing.
@mtwb47 I forgot to leave a mention here about this, but I did find the widget that was causing the issue. Same idea as yours, I ran Deckmaster through a terminal emulator and let it sit. If I remember right, I removed the window switcher widget (or whatever it's called that lets you focus to the previous window that was focused) and the issue went away. The program output gave a whole bunch of Xorg read errors, so that widget was my suspect and it seemed to be correct. But I haven't tested that out recently and have since switched to Wayland and not touched that widget.
@HoodedDeath Oh, thanks! That did it for me too. easy fixes are always the best.
Description At seemingly random times, the deckmaster process begins consuming roughly 20% of my Ryzen 7 3700X. I am currently unable to confirm if this is always the case, but for the most recent occurence, the log through systemd contians these two lines at the end:
Although this error seems to be the result of logging out and logging back in, this is the only clue I have. If needed for further info, I can run deckmaster through a normal shell instance to get more complete output. If there are verbosity options available, please inform.
Desktop:
Log Full output of
systemctl --user status streamdeck.service
:Configuration: