Blender crashing whole x11 session #106560

New Issue

Dan-C · 2023-04-04T18:05:46+02:00

Dan-C commented

2023-04-04 18:05:46 +02:00

System Information
Operating system: Linux-6.2.8-1-MANJARO-x86_64-with-glibc2.37 64 Bits
Graphics card: AMD Radeon RX 5700 XT (navi10, LLVM 15.0.7, DRM 3.49, 6.2.8-1-MANJARO) AMD 4.6 (Core Profile) Mesa 23.0.1

Blender Version
Broken: version: 3.4.1, branch: makepkg (modified), commit date: 2022-12-20 08:50, hash: rBef9ca44dee7f
Worked: -

Short description of error
Clicking inside the viewport causes a crash of the whole x11 session, effectively sending you back to the login screen.

Exact steps for others to reproduce the error
Empty scene, first few clicks do not cause a problem. After a few clicks on the default cube (selecting / unselecting) the machine does not respond anymore and the whole x11 session dies shortly after - sending you back to the login screen.
Also happens when the default cube is selected and Edit mode is enabled.
Clicking menus or the rest of the viewport does not cause a crash.
Also happening with different Kernel versions (6.1 LTS, 5.15 LTS)

**System Information** Operating system: Linux-6.2.8-1-MANJARO-x86_64-with-glibc2.37 64 Bits Graphics card: AMD Radeon RX 5700 XT (navi10, LLVM 15.0.7, DRM 3.49, 6.2.8-1-MANJARO) AMD 4.6 (Core Profile) Mesa 23.0.1 **Blender Version** Broken: version: 3.4.1, branch: makepkg (modified), commit date: 2022-12-20 08:50, hash: `rBef9ca44dee7f` Worked: - **Short description of error** Clicking inside the viewport causes a crash of the whole x11 session, effectively sending you back to the login screen. **Exact steps for others to reproduce the error** Empty scene, first few clicks do not cause a problem. After a few clicks on the default cube (selecting / unselecting) the machine does not respond anymore and the whole x11 session dies shortly after - sending you back to the login screen. Also happens when the default cube is selected and Edit mode is enabled. Clicking menus or the rest of the viewport does not cause a crash. Also happening with different Kernel versions (6.1 LTS, 5.15 LTS)

Dan-C added the

labels 2023-04-04 18:05:47 +02:00

No-Way-1 commented

2023-04-05 17:04:38 +02:00

Experiencing the same issue with the steps provided in the original report. Also found another way to reproduce.

System Information
OS: Arch Linux x86_64
Kernel: 6.2.9-arch1-1
Uptime: 1 hour, 3 mins
Resolution: 1920x1080, 1920x1080, 1920x1080, 1920x1080
DE: Plasma
WM: KWin
CPU: AMD Ryzen 7 3800X (16) @ 3.900GHz
GPU: AMD ATI Radeon RX 5600 OEM/5600 XT / 5700/5700 XT
Memory: 4130MiB / 15926MiB
Drivers: mesa 23.0.1-2, vulkan-radeon 23.0.1-2, lib32-mesa 23.0.1-2, lib32-vulkan-radeon 23.0.1-2, shaderc 2023.3-1

Blender Version
Broken: 3.5.0, blender-3.6.0-alpha+main.a76bf65c9de4-linux.x86_64-release, blender-2.93.16-linux-x64
Worked: -

Short description of error
Clicking inside the viewport, as well as entering edit mode for an object causes the GPU, and subsequently the x11 session, to crash. Relevant journalctl log attached

Exact steps for others to reproduce the error
Option 1.
As described above in the original post with the exception of 'Also happens when the default cube is selected and Edit mode is enabled.'

Option 2.
Open a new instance of Blender to a new scene. Reproducible regardless of whether or not the default cube, camera, and light are deleted. Add in an object primitive with a higher poly/vert count (e.g. a sphere or torus). Select the newly added object. Zoom in close to the object. The GPU should crash and reset, resetting the xSession.

Reproducing the issues appears to work regardless of the order in which the reproduction steps are viably performed.

Issue persists when tested with alternate kernels (older verions, LTS), older drivers, and older libraries.

Experiencing the same issue with the steps provided in the original report. Also found another way to reproduce. **System Information** OS: Arch Linux x86_64 Kernel: 6.2.9-arch1-1 Uptime: 1 hour, 3 mins Resolution: 1920x1080, 1920x1080, 1920x1080, 1920x1080 DE: Plasma WM: KWin CPU: AMD Ryzen 7 3800X (16) @ 3.900GHz GPU: AMD ATI Radeon RX 5600 OEM/5600 XT / 5700/5700 XT Memory: 4130MiB / 15926MiB Drivers: mesa 23.0.1-2, vulkan-radeon 23.0.1-2, lib32-mesa 23.0.1-2, lib32-vulkan-radeon 23.0.1-2, shaderc 2023.3-1 **Blender Version** Broken: 3.5.0, blender-3.6.0-alpha+main.a76bf65c9de4-linux.x86_64-release, blender-2.93.16-linux-x64 Worked: - **Short description of error** Clicking inside the viewport, as well as entering edit mode for an object causes the GPU, and subsequently the x11 session, to crash. Relevant journalctl log attached **Exact steps for others to reproduce the error** Option 1. As described above in the original post with the exception of 'Also happens when the default cube is selected and Edit mode is enabled.' Option 2. Open a new instance of Blender to a new scene. Reproducible regardless of whether or not the default cube, camera, and light are deleted. Add in an object primitive with a higher poly/vert count (e.g. a sphere or torus). Select the newly added object. Zoom in close to the object. The GPU should crash and reset, resetting the xSession. Reproducing the issues appears to work regardless of the order in which the reproduction steps are viably performed. Issue persists when tested with alternate kernels (older verions, LTS), older drivers, and older libraries.

journalctl.txt

3.4 KiB

Pratik Borhade added the

Platform

Linux

label 2023-04-27 15:38:56 +02:00

Jesse Yurkovich commented

2023-05-07 03:10:09 +02:00

Is this still happening? Such problems are most likely related to a bad Mesa driver (especially as it's mentioned that an old 2.93.16 version is broken too); perhaps there's an update by now.

Jesse Yurkovich added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-05-07 03:10:21 +02:00

Dan-C commented

2023-05-07 08:38:27 +02:00

Just reconfirmed that it is still happening with:
Mesa 23.0.2
Blender 3.5.0-1
Kernel 6.2.12-1

Just reconfirmed that it is still happening with: Mesa 23.0.2 Blender 3.5.0-1 Kernel 6.2.12-1

Jesse Yurkovich commented

2023-05-07 08:55:26 +02:00

Does the workaround in the following Mesa bug work for you (looks like a similar issue to yours): https://gitlab.freedesktop.org/mesa/mesa/-/issues/8781 (using the AMD_DEBUG=nooptvariant environment variable)

They have a fix but it might only be in 23.0.3, it's hard to tell with their gitlab setup.

Does the workaround in the following Mesa bug work for you (looks like a similar issue to yours): https://gitlab.freedesktop.org/mesa/mesa/-/issues/8781 (using the `AMD_DEBUG=nooptvariant` environment variable) They have a fix but it might only be in 23.0.3, it's hard to tell with their gitlab setup.

Dan-C commented

2023-05-07 09:53:39 +02:00

The env var AMD_DEBUG=nooptvariant does indeed seem to fix it.