| Summary: | Plasmashell sluggish after waking from sleep on Wayland | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Matt <mattyhoffman7> |
| Component: | generic-performance | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | 0x10c961, firlaevhans.fiete, kde, nate, simon.vogl |
| Priority: | NOR | ||
| Version: | 5.24.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Demonstration of Kickoff being slow
Journal log during slowdowns |
||
|
Description
Matt
2022-03-24 00:15:30 UTC
Can confirm this on my openSUSE Tumbleweed desktop with NVIDIA, except that it happens immediately there without even needing to hibernate xD (NVIDIA Wayland drivers as we all love them.....). Kinda hard to reproduce, though... Didn't manage to reproduce on my KDE Wayland intel laptop yet even after multiple sleeps. Cannot reproduce with current git master everything built on top of Fedora 35 with Intel UHD Graphics 620 graphics. Created attachment 147832 [details]
Journal log during slowdowns
I managed to capture a journal log of the slowdowns happening.
It also seems somewhat linked to plasmashellrc as getting rid of the [Updates] section inside of plasmashellrc fixes the bug temporarily for me....
Again, it is very hard to reproduce for me, I only managed to sporadically reproduce on NVIDIA so far, still no luck on Intel Iris Xe.
(In reply to Simon Vogl from comment #3) > Created attachment 147832 [details] > Journal log during slowdowns > > I managed to capture a journal log of the slowdowns happening. > It also seems somewhat linked to plasmashellrc as getting rid of the > [Updates] section inside of plasmashellrc fixes the bug temporarily for > me.... > Again, it is very hard to reproduce for me, I only managed to sporadically > reproduce on NVIDIA so far, still no luck on Intel Iris Xe. That journal log is interesting, because >plasmashell[17830]: QWaylandDataOffer: timeout reading from pipe >plasmashell[17830]: QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection is exactly the same as what I saw in my likely related issue (Bug 451631) that Matt linked. It sure seems suspicious and sounds like it's related to the clipboard somehow (???) If you search for QWaylandDataOffer on Bugzilla you find several other bugs that are in some way related to plasmashell hanging or crashing as well. No idea what this error means specifically but it's worth investigating IMO. I'm encountering similar sluggish behavior with plasma.
Of note, when plasma is being sluggish, I'm noticing that there might be some kind of memory leak-- I see the plasmashell process slowly fill up all available memory (not sure what the trigger is), Plasmashell goes from its standard 500-700MB to 20GB+, and eventually it causes the whole system to grind to a halt when it runs out (this happens over the course of several hours), and I have to kill the plasmashell process and restart it.
I do recall seeing something like this
> QWaylandDataOffer: timeout reading from pipe
> QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection
in the output when I restart plasmashell through a terminal.
When it starts happening again I'll see about grabbing some logs and giving a more detailed reproduction of the issue.
If you still get this issue, can you test if it happens specifically when Plasma was started with a full clipboard history and stops happening when the clipboard is cleared? Because that turned out to be the cause of my issue (read the latest comments on Bug 451631), and it would be interesting to see if these are indeed two symptoms of the same root cause. (In reply to Firlaev-Hans from comment #6) > If you still get this issue, can you test if it happens specifically when > Plasma was started with a full clipboard history and stops happening when > the clipboard is cleared? > Because that turned out to be the cause of my issue (read the latest > comments on Bug 451631), and it would be interesting to see if these are > indeed two symptoms of the same root cause. I can confirm the issue seems to only happen when there is something, anything at all, in the clipboard history. I’ve been using the computer for a lot of transcoding lately which means moving lots of video files around and making heavy use of the clipboard to do that, and I’ve been very regularly clearing the clipboard contents and noticed that ever since doing this, the sluggish behavior seems to have disappeared, and the memory leak I mentioned above is occurring at a much slower, or otherwise unnoticeable pace. To be honest I’m not sure if the memory leak is related to the issue, but I thought I should mention it in case anyone notices it too. When I have time to do a more in depth (read: scientific, with steps and manipulating different variables separately to try and deliberately cause the issue to happen), I’ll post my findings if someone else doesn’t discover the root cause before then. One of the system updates within the past few weeks seems to have fixed the sluggish behavior tied to the clipboard that I was experiencing before. I can't reproduce the bug anymore. KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 QT Version: 5.15.5 Kernel Version: 5.19.5-1-Manjaro Graphics Platform: Wayland Unknown what was causing the issue exactly, but it seems to be fixed now. Ah I bet it was Bug 454379. *** This bug has been marked as a duplicate of bug 454379 *** |