Crash without warning when opening material properties panel. #108455

New Issue

Ivo van der Lans · 2023-05-31T13:15:17+02:00

Ivo van der Lans commented

2023-05-31 13:15:17 +02:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: AMD Radeon RX 540 Series, ATI Technologies Inc., OpenGL, 4.5.0 Core Profile Context 22.20.16.03.220829

Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: 55485cb379
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1
Worked: no newer version works.

Short description of error
We get a hard crash without warning when opening the material properties panel in the "Layout" workspace right after startup (i.e. with a clean "General" new file). Opening the material properties panel in other workspaces causes the same crash.

I suspect that this is an EEVEE problem since opening other properties panels (which do not have the material preview) works fine and opening the material properties panel after having selected the Cycles engine in the "Render properties" panel also works fine. Somehow, it feels like being a hardware problem, but I cannot explain why. Interestingly, the device for rendering in the [Preferences][System] is set to ""None" and no GPU's are available in the Cuda, OptiX, HIP, and oneAPI sections.

When switching the viewport in the "Layout" workspace to "Viewport Shading" (i.e. rendered by EEVEE), Blender crashes. When Cycles is selected as rendering engine, then "Viewport Shading" works fine.

The crash happens on my colleague's computer in India to which I have no direct access. Updating graphics drivers is not easily possible due to company constraints. My colleague now uses the Cycles rendering engine by default. Some current file of her was saved with the default EEVEE setting, so she cannot load the file without crashing Blender; I have now modified the file on my computer by switching it to Cycles rendering which bypasses that problem for now.

Exact steps for others to reproduce the error

[Based on the default startup]:

Open Blender.
Select "General" new file
Open the "Material properties" panel in the "Layout" workspace.
Blender crashes.

[Based on the default startup]:

Open Blender.
Select "General" new file
Select "Viewport Shading" in the "Layout" workspace.
Blender Crashes.

[Based on the default startup]:

Open Blender.
Load a previously stored blend file with EEVEE set as the renderer (and I suspect showing the "Materials properties panel" or the viewport in "Viewport Shading" mode).
Blender Crashes.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: AMD Radeon RX 540 Series, ATI Technologies Inc., OpenGL, 4.5.0 Core Profile Context 22.20.16.03.220829 **Blender Version** Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: 55485cb379f7 Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3 Worked: no newer version works. **Short description of error** We get a hard crash without warning when opening the material properties panel in the "Layout" workspace right after startup (i.e. with a clean "General" new file). Opening the material properties panel in other workspaces causes the same crash. I suspect that this is an EEVEE problem since opening other properties panels (which do not have the material preview) works fine and opening the material properties panel after having selected the Cycles engine in the "Render properties" panel also works fine. Somehow, it feels like being a hardware problem, but I cannot explain why. Interestingly, the device for rendering in the [Preferences][System] is set to ""None" and no GPU's are available in the Cuda, OptiX, HIP, and oneAPI sections. When switching the viewport in the "Layout" workspace to "Viewport Shading" (i.e. rendered by EEVEE), Blender crashes. When Cycles is selected as rendering engine, then "Viewport Shading" works fine. The crash happens on my colleague's computer in India to which I have no direct access. Updating graphics drivers is not easily possible due to company constraints. My colleague now uses the Cycles rendering engine by default. Some current file of her was saved with the default EEVEE setting, so she cannot load the file without crashing Blender; I have now modified the file on my computer by switching it to Cycles rendering which bypasses that problem for now. **Exact steps for others to reproduce the error** [Based on the default startup]: - Open Blender. - Select "General" new file - Open the "Material properties" panel in the "Layout" workspace. - Blender crashes. [Based on the default startup]: - Open Blender. - Select "General" new file - Select "Viewport Shading" in the "Layout" workspace. - Blender Crashes. [Based on the default startup]: - Open Blender. - Load a previously stored blend file with EEVEE set as the renderer (and I suspect showing the "Materials properties panel" or the viewport in "Viewport Shading" mode). - Blender Crashes.

system-info-3.4.1.txt

14 KiB

system-info-3.5.1.txt

14 KiB

Ivo van der Lans added the

labels 2023-05-31 13:15:17 +02:00

YimingWu commented

2023-06-01 04:28:34 +02:00

Your GPU should have no problem running blender correctly. Could you try launching blender with blender -d --debug-gpu and give us the output? See here for details: https://docs.blender.org/manual/en/latest/advanced/command_line/arguments.html#gpu-options

Thanks!

Your GPU should have no problem running blender correctly. Could you try launching blender with `blender -d --debug-gpu` and give us the output? See here for details: https://docs.blender.org/manual/en/latest/advanced/command_line/arguments.html#gpu-options Thanks!

YimingWu added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-06-01 04:28:42 +02:00

Ivo van der Lans commented

2023-06-01 08:33:23 +02:00

Thanks for your fast response. I have ran the command you asked me to, on my colleague's system while piping the stdout and stderr outputs to separate files which I attached to this comment.

report_std.txt

62 KiB

report_err.txt

14 KiB

YimingWu commented

2023-06-01 08:49:00 +02:00

Thanks for the feedback!

@fclem might want to take a look: extension not supported: GL_AMD_vertex_shader_layer

Thanks for the feedback! @fclem might want to take a look: `extension not supported: GL_AMD_vertex_shader_layer`

Ivo van der Lans commented

2023-07-07 16:23:36 +02:00

Today, I understood that the 2nd graphics card (Radeon) in my colleague's system (mentioned above) cause a crash in another software too. We were able to circumvent the crash by disabling the Radeon card in window's device manager. Without the Radeon (but still using the built-in Intel UHD Graphics 620 card, that other software started working again. I will ask If my colleague can now replay the scenario we found in Blender without it crashing. I now suspect that the Radeon card is either faulty or doesn't comply to OpenGL standards.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Crash without warning when opening material properties panel. #108455