Lost connection to Wayland compositor under heavy cpu load

Distribution

Arch Linux x86_64

Package version

6.2.8

Frequency

Quite often

Bug description

Under heavy cpu load it happens quite often that nemo closes itself when I'm trying to open a next video in my videos folder, this folder contains about 9k videos.

The last message that gets printed is Gdk-Message: 19:01:56.883: Lost connection to Wayland compositor. and then exits with code 1.

Steps to reproduce

1. Spike cpu: e.g. doing a multicore compile of large c++ projects or a rust project.
2. Open a file.
3. quickly try to open another, nemo will appear to not have registered the click, keep clicking a couple times and it might crash.
4. repeat 2 and 3 until nemo quits, for me it takes around 1-3 tries under 100% cpu load.

Expected behavior

I'd accept nemo to be laggy but not that it'd force quit on me.

Additional information

I've had this happen during normal pc usage too which might've been the same cause.
I use WM: sway v1.10, other programs dont behave like this for me

No source files or tests are named. Start by reproducing the crash using the listed CPU-load steps on Arch Linux with sway, then inspect Nemo's behavior when the Wayland connection is lost. Done means opening successive videos under load no longer causes Nemo to exit unexpectedly.