Bug 449805

Summary: KWIN_WAYLAND 5.23.5 Crashed while sharing desktop
Product: [Plasma] kwin Reporter: temptempor
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash CC: nate
Priority: NOR    
Version First Reported In: 5.23.5   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description temptempor 2022-02-08 18:44:52 UTC 
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
***
Crashed while sharing desktop in Teams session through Microsoft Edge stable.

STEPS TO REPRODUCE
1. Microsoft Edge Version 96.0.1054.62 
2. Microsoft Teams web
3. Hop-in/out desktop sharing session (whole screen)

OBSERVED RESULT
The first times it was fine. Then suddenly it crashed.

***
           PID: 4652 (kwin_wayland)
           UID: 1000 (_USERNAME_)
           GID: 1000 (_USERNAME_)
        Signal: 11 (SEGV)
     Timestamp: Tue 2022-02-08 18:58:39 CET (16min ago)
  Command Line: /bin/kwin_wayland --wayland_fd 5 --socket wayland-0 --xwayland-fd 7 --xwayland-fd 6 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_RylnXF --xwayland /usr/lib/startplasma-waylandsession
    Executable: /usr/bin/kwin_wayland
 Control Group: /user.slice/user-1000.slice/session-4.scope
          Unit: session-4.scope
         Slice: user-1000.slice
       Session: 4
     Owner UID: 1000 (_USERNAME_)
       Boot ID: b37a56969b2a481faa6a154b8b194388
    Machine ID: 878efc2d7b2c47a38290b3d281b1fc77
      Hostname: _HOSTNAME_
       Storage: /var/lib/systemd/coredump/core.kwin_wayland.1000.b37a56969b2a481faa6a154b8b194388.4652.1644343119000000.zst (truncated)
     Disk Size: 12.8M
       Message: Process 4652 (kwin_wayland) of user 1000 dumped core.

***

Unfortunately it'd appear the core dump is not complete somehow.

https://transfert.free.fr/aJ91KU

***
févr. 08 18:58:39 _HOSTNAME_ audit[4652]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=4 pid=4652 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1
févr. 08 18:58:39 _HOSTNAME_ kernel: kwin_wayland[4652]: segfault at 0 ip 00007f6d20b64781 sp 00007ffde279f250 error 6 in libkwinglutils.so.5.23.5[7f6d20b55000+12000]
févr. 08 18:58:39 _HOSTNAME_ kernel: Code: ff 0f 1f 84 00 00 00 00 00 49 63 c6 48 8d 04 c3 45 85 f6 0f 8e 5d ff ff ff f3 0f 10 45 00 48 83 c5 08 48 83 c3 08 48 83 c2 10 <f3> 0f 11 42 f0 f3 0f 10 45 fc f3 0f 11 42 f4 f3 0f 10 43 f8 f3 0f
févr. 08 18:58:39 _HOSTNAME_ kernel: audit: type=1701 audit(1644343119.095:346): auid=1000 uid=1000 gid=1000 ses=4 pid=4652 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1
***

EXPECTED RESULT
It should never crash ideally?

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.7-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 62.7 Gio of RAM
Graphics Processor: AMD Radeon RX 6900 XT

ADDITIONAL INFORMATION
The session was "barren" at that time, litterally nothing else running but a couple of terminals. Had just rebooted from a month long X11 session after updates.
Comment 1 Nate Graham 2022-02-08 19:20:53 UTC 
If something crashed, we need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Can you please attach one? Thanks!
Comment 2 temptempor 2022-02-08 20:21:36 UTC 
(In reply to Nate Graham from comment #1)
> If something crashed, we need a backtrace of it so we can figure out what's
> going on. See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports
> 
> Can you please attach one? Thanks!

Hi,
I only have this Coredump:

> https://transfert.free.fr/aJ91KU

And unfortunately, the process execeeded my Coredump limits so it would appear the main thread was not included:

***
warning: Error reading shared library list entry at 0x6f635f74696e6900
Failed to read a valid object file image from memory.
Core was generated by `/bin/kwin_wayland --wayland_fd 5 --socket wayland-0 --xwayland-fd 7 --xwayland-'.
Program terminated with signal SIGSEGV, Segmentation fault.

warning: Section `.reg-xstate/4652' in core file too small.
#0  0x00007f6d20b64781 in ?? ()
[Current thread is 1 (LWP 4652)]
(gdb) bt
#0  0x00007f6d20b64781 in ?? ()
Backtrace stopped: Cannot access memory at address 0x7ffde279f250
***

I don't know if you can make anything of this. People at systemd seem to think these are still usable somehow...
https://github.com/systemd/systemd/issues/3883#issuecomment-239106337
Comment 3 Nate Graham 2022-02-08 20:55:10 UTC 
Dunno if there is anything we can do with this, unfortunately. I would recommend increasing your coredump limit, then reproduce the crash and attach a complete backtrace, if you can.
Comment 4 Bug Janitor Service 2022-02-23 04:36:34 UTC 
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!
Comment 5 Bug Janitor Service 2022-03-10 04:35:45 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!