Xwayland crash, signal 6

[shacharr-microsoft]

Environment

Windows build number: Microsoft Windows [Version 10.0.21349.1000]
Your Distribution version: Ubuntu 20.04
Your WSLg version: 0.2.15

Steps to reproduce

Run emacs and edit code for a while. Emacs window eventually disappeared, with dmesg containing:
weston.log
pulseaudio.log

[23485.764003] potentially unexpected fatal signal 6.
[23485.764008] CPU: 0 PID: 441 Comm: Xwayland Not tainted 5.4.91-microsoft-standard-WSL2 #1
[23485.764083] RIP: 0033:0x7f25d0e62115
[23485.764087] Code: c2 b8 ea 00 00 00 0f 05 48 3d 00 f0 ff ff 77 3d 41 89 c0 41 ba 08 00 00 00 31 d2 4c 89 ce bf 02 00 00 00 b8 0e 00 00 00 0f 05 <48> 8b 84 24 08 01 00 00 64 48 33 04 25 28 00 00 00 75 24 44 89 c0
[23485.764092] RSP: 002b:00007ffca8ab9230 EFLAGS: 00000246 ORIG_RAX: 000000000000000e
[23485.764096] RAX: 0000000000000000 RBX: 0000559b448809f0 RCX: 00007f25d0e62115
[23485.764098] RDX: 0000000000000000 RSI: 00007ffca8ab9230 RDI: 0000000000000002
[23485.764101] RBP: 0000559b437ce43e R08: 0000000000000000 R09: 00007ffca8ab9230
[23485.764103] R10: 0000000000000008 R11: 0000000000000246 R12: 00007ffca8ab94c0
[23485.764105] R13: 00007ffca8ab9890 R14: 00007ffca8ab9968 R15: 00007ffca8ab988c
[23485.764108] FS: 00007f25d07f3440 GS: 0000000000000000

WSL logs:

• Attach WSLg logs from /mnt/wslg

You can access the wslg logs using explorer at: \\wsl\<Distro-Name>\mnt\wslg (eg: \\wsl\Ubuntu-20.04\mnt\wslg)

• puseaudio.log
• weston.log
• versions.txt

$ sudo cat /mnt/wslg/versions.txt
[sudo] password for shacharr:
WSLg ( x86_64 ): 0.2.15+Branch.master.Sha.0f60d20b141a4bd39162b6e2e9f5ff3a074d1d06
Mariner: VERSION="1.0.20210224"
FreeRDP: 000d25814f3e48b6c3c0e524d8eb21ed819519fb
weston: bbdc70a6d800a0deb29c728703e3c056c2c24222
pulseaudio: 2f0f0b8c3872780f15e275fc12899f4564f01bd5
mesa:
sharedguestalloc: ebd000e3cb2649b7c28d1b71f76d43f592b45a61

Expected behavior

No crash

Actual behavior

Xwayland crush, much sadness ensued

[hideyukn88]

attach weston.log which lost in trasnfer.

weston.log

[spronovo]

This should be fixed with v1.0.19 that we just released moments ago. To update your WSL install, make sure to save your work than type the following from an elevated command prompt in Windows:

wsl --shutdown
wsl --update