Bug 478094 - kwin_wayland crashes when toggling desktop grid effect in multi-monitor setup
Summary: kwin_wayland crashes when toggling desktop grid effect in multi-monitor setup
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: effects-desktop-grid (show other bugs)
Version: master
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2023-12-05 06:17 UTC by fanzhuyifan
Modified: 2023-12-09 02:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
backtrace (171.04 KB, text/plain)
2023-12-05 06:17 UTC, fanzhuyifan 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description fanzhuyifan 2023-12-05 06:17:40 UTC 
Created attachment 163892 [details]
backtrace

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Create 9 desktops in a 3x3 grid
2. Create a lot of windows on the external monitor (I ran seq 1 30 | xargs -I{} bash -c "xclock -geometry 200x200 &")
3. Go to another desktop and trigger desktop grid effect
4. Repeat step 3.

OBSERVED RESULT
kwin_wayland crashes (see attachment for gdb backtrace)

EXPECTED RESULT
kwin_wayland shouldn't crash

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.0
Kernel Version: 6.2.0-37-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i9-13900H
Memory: 15.2 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Zephyrus G16 GU603VV_GU603VV
System Version: 1.0

ADDITIONAL INFORMATION

For me this is reproducible with high probability.
Also happened on my arch linux machine running master build.

The output of my kscreendoctor -o:

Output: 1 eDP-1
        enabled
        connected
        priority 1
        Panel
        Modes:  0:2560x1600@240*!  1:2560x1600@60  2:1600x1200@60  3:1280x1024@60  4:1024x768@60  5:2560x1600@60  6:1920x1200@60  7:1280x800@60  8:2560x1440@60  9:1920x1080@60  10:1600x900@60  11:1368x768@60  12:1280x720@60 
        Geometry: 1920,0 1707x1067
        Scale: 1.5
        Rotation: 1
        Overscan: 0
        Vrr: Automatic
        RgbRange: Automatic
        HDR: incapable
        Wide Color Gamut: incapable
        ICC profile: none
Output: 2 HDMI-A-1
        enabled
        connected
        priority 2
        HDMI
        Modes:  0:1920x1080@60*!  1:1920x1080@72  2:1920x1080@60  3:1920x1080@50  4:1680x1050@60  5:1600x900@60  6:1280x1024@60  7:1440x900@60  8:1280x800@60  9:1280x720@60  10:1280x720@60  11:1280x720@50  12:1024x768@70  13:1024x768@60  14:800x600@72  15:800x600@60  16:800x600@56  17:720x576@50  18:720x480@60  19:640x480@73  20:640x480@60 
        Geometry: 0,0 1920x1080
        Scale: 1
        Rotation: 1
        Overscan: 0
        Vrr: incapable
        RgbRange: unknown
        HDR: incapable
        Wide Color Gamut: incapable
        ICC profile: none
Comment 1 fanzhuyifan 2023-12-05 06:45:32 UTC 
I also trigger this without fractional scaling:

Output: 1 eDP-1
        enabled
        connected
        priority 1
        Panel
        Modes:  0:2560x1600@240*!  1:2560x1600@60  2:1600x1200@60  3:1280x1024@60  4:1024x768@60  5:2560x1600@60  6:1920x1200@60  7:1280x800@60  8:2560x1440@60  9:1920x1080@60  10:1600x900@60  11:1368x768@60  12:1280x720@60 
        Geometry: 1920,0 2560x1600
        Scale: 1
        Rotation: 1
        Overscan: 0
        Vrr: Automatic
        RgbRange: Automatic
        HDR: incapable
        Wide Color Gamut: incapable
        ICC profile: none
Output: 2 HDMI-A-1
        enabled
        connected
        priority 2
        HDMI
        Modes:  0:1920x1080@60*!  1:1920x1080@72  2:1920x1080@60  3:1920x1080@50  4:1680x1050@60  5:1600x900@60  6:1280x1024@60  7:1440x900@60  8:1280x800@60  9:1280x720@60  10:1280x720@60  11:1280x720@50  12:1024x768@70  13:1024x768@60  14:800x600@72  15:800x600@60  16:800x600@56  17:720x576@50  18:720x480@60  19:640x480@73  20:640x480@60 
        Geometry: 0,0 1920x1080
        Scale: 1
        Rotation: 1
        Overscan: 0
        Vrr: incapable
        RgbRange: unknown
        HDR: incapable
        Wide Color Gamut: incapable
        ICC profile: none


This is also triggered without opening a ton of windows.
Comment 2 fanzhuyifan 2023-12-05 21:09:34 UTC 
Also crashed when toggling the overview effect. Saw this in my journal:

Dec 05 13:05:28 arch kwin_wayland[8939]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Dec 05 13:05:28 arch kwin_wayland[8939]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"

And this in my dmesg:

[Dec 5 13:05] [drm] [nvidia-drm] [GPU ID 0x00000100] Framebuffer memory not appropriate for scanout
[  +0.000143] [drm] [nvidia-drm] [GPU ID 0x00000100] Framebuffer memory not appropriate for scanout


Not 100% sure if this is the same bug though.
Comment 3 fanzhuyifan 2023-12-05 21:12:12 UTC 
Also crashed when toggling the overview effect. Saw this in my journal:

Dec 05 13:05:28 arch kwin_wayland[8939]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Dec 05 13:05:28 arch kwin_wayland[8939]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"

And this in my dmesg:

[Dec 5 13:05] [drm] [nvidia-drm] [GPU ID 0x00000100] Framebuffer memory not appropriate for scanout
[  +0.000143] [drm] [nvidia-drm] [GPU ID 0x00000100] Framebuffer memory not appropriate for scanout

There messages are also seen when the crash is triggered by desktop grid.
Comment 4 fanzhuyifan 2023-12-09 02:33:16 UTC 
Hasn't happened to me for a while. Maybe it has been fixed.