gnome-shell gets killed by kernel because its real-time KMS thread exceeds 200ms of CPU usage

Xwayland exit with code 1 when I launch Division 2

In gdb it looks like this:

7.fc40.x86_64/misc/../sysdeps/unix/sysv/linux/epoll_wait.c
30        return SYSCALL_CANCEL (epoll_wait, epfd, events, maxevents, timeout);                                                                                                                                   
(gdb) c
Continuing.

Thread 1 "Xwayland" received signal SIGPIPE, Broken pipe.
0x00007f6dd71159fb in __GI___writev (iovcnt=1, iov=0x7fff1ee13710, fd=59) at ../sysdeps/unix/sysv/linux/writev.c:26
Downloading source file /usr/src/debug/glibc-2.38.9000-7.fc40.x86_64/misc/../sysdeps/unix/sysv/linux/writev.c
26        return SYSCALL_CANCEL (writev, fd, iov, iovcnt);                                                                                                                                                         
(gdb) c
Continuing.
[Thread 0x7f6dd571b6c0 (LWP 6876) exited]
[Thread 0x7f6dd4f1a6c0 (LWP 6877) exited]
[Thread 0x7f6dd5f5d6c0 (LWP 6875) exited]
[Thread 0x7f6dcb5fd6c0 (LWP 6874) exited]
[Thread 0x7f6dcadfc6c0 (LWP 6873) exited]
[Thread 0x7f6dcbdfe6c0 (LWP 6872) exited]
[Thread 0x7f6dcc5ff6c0 (LWP 6871) exited]
[Inferior 1 (process 6866) exited with code 01]
(gdb) q

Of course when it happens I lost my gnome session with all unsaved data.

What means exit of Xwayland process with code 1?

xwayland-valgrind.txt

❯ rpm -qa | grep Xwayland | sort
xorg-x11-server-Xwayland-23.2.0-2.fc40.x86_64
xorg-x11-server-Xwayland-debuginfo-23.2.0-2.fc40.x86_64
xorg-x11-server-Xwayland-debugsource-23.2.0-2.fc40.x86_64