Bug 436240 - Lag/hang in apps and Plasma when a notification appears while compositing is active and using a non-NVIDIA GPU
Summary: Lag/hang in apps and Plasma when a notification appears while compositing is ...
Status: REOPENED
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 5.27.11
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-26 20:47 UTC by Ilya Bizyaev
Modified: 2024-03-21 20:32 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ilya Bizyaev 2021-04-26 20:47:40 UTC
SUMMARY
When a notification starts drawing (yes, it's a slow process here) and I'm using Firefox, both mouse and keyboard input are effectively blocked until the notification is displayed. When it's done drawing, the events get delivered, but the 3-4 second lag that it causes is annoying.

STEPS TO REPRODUCE
1. Do something in Firefox
2. Receive a notification while typing

OBSERVED RESULT
The input is delayed until the notification finishes rendering


EXPECTED RESULT
The input continues as normal


SOFTWARE/OS VERSIONS
Operating System: openSUSE Leap 15.2
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2
Graphics Platform: X11
Comment 1 Nate Graham 2021-04-27 19:44:05 UTC
wat

Is is causing the CPU to spike to 100% or something?
Comment 2 Ilya Bizyaev 2021-04-27 19:45:03 UTC
No, the resource usage seems to stay as usual...
Comment 3 Nate Graham 2021-07-06 14:32:46 UTC

*** This bug has been marked as a duplicate of bug 414785 ***
Comment 4 Ilya Bizyaev 2021-07-07 05:20:22 UTC
Reopening to keep it separate from the NVIDIA report, as people there seem to have high CPU load when notifications are displayed.

I have an Intel iGPU.
Comment 5 Toby Fox 2021-07-07 08:34:47 UTC
I commented on the other bug, but this one resembles mine more: I have an NVIDIA GPU but it's switched-off and I only use my Intel iGPU. No CPU spike, and just one notification causes it. Doesn't happen only on Firefox for me though, happens with everything.
Comment 6 Nate Graham 2021-07-07 13:00:21 UTC
What Intel GPU specifically do you have?

And what is the rendering method in System Settings > Display & Monitor > Compositor?

Finally, can you open the hidden "Plasma Renderer" settings window by searching for "Plasma Renderer" in KRunner of Kickoff and opening it, and then mention what the values in the two comboboxes are?
Comment 7 Ilya Bizyaev 2021-07-07 15:51:36 UTC
Intel® Core™ i5-10210U, Intel® UHD Graphics (CometLake-U GT2), i915 driver

OpenGL 3.1

Auto
Comment 8 Nate Graham 2021-07-07 16:06:25 UTC
Thanks. I have the same GPU and chipset (Comet lake) and the same plasma renderer settings. But I'm using OpenGL 2.0, which I believe is the default, rather than OpenGL 3.1, as you're using.

I switched to OpenGL 3.1 but could not reproduce the lag when a notification appears. Can you try to change to 2.0 and see if the issue goes away?
Comment 9 Toby Fox 2021-07-07 16:29:31 UTC
I have an NVIDIA GeForce GTX 960M GPU (disabled with bbswitch) and Intel HD Graphics 530 iGPU (CPU is Intel i5-6300HQ). I'm also using OpenGL 3.1 and have Automatic in both the Plasma Renderer options.

Changing compositor to use OpenGL 2.0 didn't fix the issue for me. However, that did inspire me to check disabling the compositor entirely, and that does fix the issue.
Comment 10 Nate Graham 2021-07-07 23:33:20 UTC
Thanks folks. Moving to KWin, as it seems related to compositing.
Comment 11 Michael Hamilton 2021-10-15 00:15:19 UTC
This is very easy to reproduce, in a konsole do:

for i in 1 2 3 4 5 6 7 8 9 10; do notify-send --expire-time 20000 test $i;done

With --expire-time 0 (no expiry at all) there seems to be no impact on CPU or responsiveness.  So it appears to have something to do with the way expiry is implemented.
Comment 12 Ilya Bizyaev 2024-03-16 16:07:29 UTC
I haven't had this problem in a long time, so I will close this report
Comment 13 Daniel Eckl 2024-03-21 20:08:02 UTC
I have this problem every day and I don't understand why it can be closed just if one person hasn't seen it for some time.

If one needs a recent reproduction scenario then please just ask.
Comment 14 Ilya Bizyaev 2024-03-21 20:31:23 UTC
I closed it because I'm the one who reported it in the first place, and there has been no activity in 3 years, which led me to think that no new users are experiencing this.

I'm glad that you have found time to reopen it, but then please also update the fields with up-to-date version info.