https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #81 from Alexander Schlarb <alexander-kde@ninetailed.ninja> --- @Nate Graham: > I'm also wondering if there's any disadvantage to always using the threaded > render loop. Alexander, would you be able to run with it for a while and > report any regressions, if any? I've been running my entire KDE Desktop session with `QSG_RENDER_LOOP=threaded` set in `.pam_environment` for the last month and it only had an effect on Plasma's (invisible) memory usage. Everything else is working as before (i.e.: KWin still has its share of issues –particularily on Wayland – but it's not worse than before either). As a matter of fact with this bug it's so bad I wouldn't be using Plasma at all (like I did for 2 months before finding this solution) if the issue wouldn't have been fully resolved by this. @David Edmundson: > Is decided by Qt based on your graphic card/drivers. I did some digging in the Qt source code on why this is disabled and it mostly seems to be because of a bug in an old (pre-2014) version of `libxcb` that caused issues for MESA. I filled a bug with Qt to suggest reevaluating that blacklist entry – we'll see what they say: https://bugreports.qt.io/browse/QTBUG-67277 > Maybe that selection code in Qt can be tweaked, but we most definitely > shouldn't force it from our side. If Qt decides that it's safe to remove that blacklist entry for 5.11+ or maybe just 5.12+, then forcing this from Plasmashell's side for older should IMHO be considered (with an appropriate version guard and comment so that's its easy to remove once support for these versions is dropped of course). -- You are receiving this mail because: You are watching all bug changes.
