Blender crashes system on debian 11 when attempting to move around camera

[ServerBBQ]

Specs:

OS: Debian GNU/Linux 11 (bullseye) x86_64 
Kernel: 5.10.0-21-amd64 
Resolution: 1920x1080 
DE: GNOME 3.38.6 
CPU: AMD Ryzen 5 5600 (12) @ 3.500GHz 
GPU: AMD ATI Radeon RX 5600 XT
Memory: 32014MiB

Troubleshooting steps:

• installed blender from official website and done steps below
  • worked so this narrows it down to the flatpak being the * problem
• disabled gpu acceleration via flatseal
  • worked but very laggy
• booted from live iso file to see if the issue is related to any of the packages installed on my system
  • showed same issue as on my normal install

Steps to reproduce:

1. boot off of the debian-live-11.6.0-amd64-gnome+nonfree iso(https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.6.0-live+nonfree/amd64/bt-hybrid/)
2. install flatpak using instructions from https://flatpak.org/setup/Debian and logout instead of restarting to complete setup
3. install flatseal and blender from flathub
4. go into flatseal and disable wayland for blender(blender doesn't launch on wayland with gnome 3.38)
5. launch blender, open a demo file(I used Lone Monk from https://www.blender.org/download/demo-files/)
6. move camera around and observe crash

Image of crash:

[kevinsmia1939]

By crashes system, did you mean the whole OS crash or just blender?
Can you run blender in terminal to see if there is any error?
flatpak run org.blender.Blender

[ServerBBQ]

Yes whole os crashes, I need to hard reset every time this happens.

It didn't crash when running it via the terminal. Edit: it was a fluke
I decided to try running the command from the .desktop file and it crashed
/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=blender --file-forwarding org.blender.Blender @@ @@

logs:

Failed to open dir (No such file or directory): /run/user/1000/gvfs/
amdgpu: amdgpu_cs_query_fence_status failed.
amdgpu: The CS has been rejected (-125), but the context isn't robust.
amdgpu: The process will be terminated.
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
blender: ../external_epoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed.
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.

[kevinsmia1939]

It is rather hard to tell, it could be issue with blender that show memory leak.

[poperigby]

I'm having the same issue on Fedora Kinoite 38 with an RX 5700 XT.