https://bugs.kde.org/show_bug.cgi?id=503827
--- Comment #7 from nyanpasu64 <[email protected]> --- Incredibly I've found that *playing* the second file *on another computer* (in Audacious) can *remotely* trigger >100% CPU usage. - Both computers are running KDE and linked via KDE Connect. - I played 2album.flac in Audacious media player (VLC should also work?). I think this transmits the album art to the computer sitting on its lock screen. - Pausing the player stops CPU burn until I next stop and start playback (unpausing doesn't resume CPU burn). I suspect this is because the lock screen defaults to "No title\n Choose player automatically". The CPU burn only happens when the screen is *black*. If I wait for the password field to disappear (but the clock is still visible), then start playback, I can no longer trigger CPU burn (even with screen off) until I unlock and lock the screen again. I think this is because the album art QQuickImage gains a "stable" size (rather than infinitely looping) and keeps it for the remainder of the process lifetime. -- You are receiving this mail because: You are watching all bug changes.
