Summary: | Plasmashell is freezing when laptop is connected to an external monitor | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | mrigs <mriganka13484+tux> |
Component: | generic-multiscreen | Assignee: | Aleix Pol <aleixpol> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | develop, ilmari.lauhakangas, jean, klimciauskasnikas, nate, plasma-bugs |
Priority: | NOR | ||
Version: | 5.15.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Mageia RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | Plasma 6.0 | |
Attachments: | Plasmashell backtrace while hanging |
Description
mrigs
2020-11-12 06:00:20 UTC
It also 1) freezes without any involvement of an external monitor 2) does not freeze with 4.19 kernel For more information and confirmations, see https://forum.kde.org/viewtopic.php?f=289&t=164123 Switching to another tty with Ctrl-Alt-F2 often works, but not always. If it works, switching back to the original tty heals the freeze. Same bug on kubuntu 20.10, plasma version 5.19.5, after a while memory starts going up and then the system freezes, the highest i recorded memory usage was 6gb, also, restarting the plasma resets the usage. Can someone affected get a backtrace of what plasmashell was doing when it hung? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Created attachment 141080 [details]
Plasmashell backtrace while hanging
I attached a plasmashell backtrace. Plasmashell was frozen at that point, i.e. the task bar was not reacting, there was no visual progress of time etc. I'm using Gentoo Linux with Linux 5.10.52, KDE 5.21.5, Qt 5.15.2 and Mesa 21.1.7. I use the Intel i915 driver. Unfortunately, on this system I do not have detailed debugging symbols available at present.
Thanks. Looks like it's stuck in QSGThreadedRenderLoop::polishAndSync(). I wonder... can you try again with the "Basic" (unthreaded) render loop? You can access this setting in the hidden "Plasma Renderer" settings window, which yo can find by searching for "Plasma Renderer" in Kickoff or KRunner. Are you using an NVIDIA GPU, by any chance? I will try the non-threaded render loop, but presumable I won't have new results until next week. And no, unfortunately (or fortunately?) I do not use an NVIDIA GPU. It's the Intel HD Graphics 520 being part of the Intel i5-6200U notebook CPU (Skylake architecture). OK, if you're not using an NVIDIA GPU, then it's probably not that other known issue with NVIDIA GPUs and the threaded render loop. After changing the setting to the non-threaded render loop, I haven't had any freezes so far. Am I supposed to encounter any other problems with that setting (with the exception of, say, performance issues)? Are there any known pitfalls? Or can I simply use it "as is" without ever changing it back? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This will be fixed automatically in Qt6, but unfortunately we can't just use the basic render look unconditionally in Qt 5 since it causes other regressions. :( |