Metal backend crashes entire macOS when Contact Shadows are enabled and Clearcoat materials are visible in the scene #109342

New Issue

Matthias · 2023-06-25T14:55:37+02:00

Matthias commented

2023-06-25 14:55:37 +02:00

System Information
Operating system: macOS 13.4.1
Computer: Mac Pro (2019) 3,3 GHz 12 Core Intel Xeon W, 96 GB Memory
Graphics card: AMD Radeon Pro W5700X 16 GB

Blender Version
Broken: 3.5, 3.6, 4.0
Worked: worked definitely with Blender 3.5 before, so it must be related to a recent macOS version update

Short description of error
With Metal backend enabled and EEVEE rendering in viewport turned on. Blender becomes unresponsive when any light has "Contact Shadows" enabled and a material with Principled Shader is visible in the scene where the Clearcoat value is not 0.0.
In case Blender is not "force quited" within the next 2-3 seconds the GPU starts to produce glitches in the entire macOS UI and the whole computer is becoming unresponsive und ultimately crashes.
This is very strange behaviour but can be reproduced reliantly (see below). I did not encounter this issue with the Metal Backend at the beginning when it was introduced and also not during the 3.5 beta phase. I assume it is a bug that got introduced by a recent macOS update. I also assume that it only occurs on Intel/AMD platforms, otherwise I assume it would have been reported already.

Exact steps for others to reproduce the error

Open Blender with default scene (with Metal backend enabled)
Turn on EEVEE viewport rendering for the default viewport
Select default Point Light and go into light properties
under Shadow section enable "Contact Shadows"
Select Default Cube and open Shader editor for Default material
In Default Principled BSDF Shader enter 1.0 in Clearcoat field
--> Blender becomes unresponsive immediately, GPU glitches occur, system becomes unresponsive, computer crashes

A similar crash behaviour is also experienced when then a Transmission value is entered that is not 0.0. All other Principled BSDF parameter do not cause any crashes.

**System Information** Operating system: macOS 13.4.1 Computer: Mac Pro (2019) 3,3 GHz 12 Core Intel Xeon W, 96 GB Memory Graphics card: AMD Radeon Pro W5700X 16 GB **Blender Version** Broken: 3.5, 3.6, 4.0 Worked: worked definitely with Blender 3.5 before, so it must be related to a recent macOS version update **Short description of error** With Metal backend enabled and EEVEE rendering in viewport turned on. Blender becomes unresponsive when any light has "Contact Shadows" enabled and a material with Principled Shader is visible in the scene where the Clearcoat value is not 0.0. In case Blender is not "force quited" within the next 2-3 seconds the GPU starts to produce glitches in the entire macOS UI and the whole computer is becoming unresponsive und ultimately crashes. This is very strange behaviour but can be reproduced reliantly (see below). I did not encounter this issue with the Metal Backend at the beginning when it was introduced and also not during the 3.5 beta phase. I assume it is a bug that got introduced by a recent macOS update. I also assume that it only occurs on Intel/AMD platforms, otherwise I assume it would have been reported already. **Exact steps for others to reproduce the error** - Open Blender with default scene (with Metal backend enabled) - Turn on EEVEE viewport rendering for the default viewport - Select default Point Light and go into light properties - under Shadow section enable "Contact Shadows" - Select Default Cube and open Shader editor for Default material - In Default Principled BSDF Shader enter 1.0 in Clearcoat field --> Blender becomes unresponsive immediately, GPU glitches occur, system becomes unresponsive, computer crashes A similar crash behaviour is also experienced when then a Transmission value is entered that is not 0.0. All other Principled BSDF parameter do not cause any crashes.

Matthias added the

labels 2023-06-25 14:55:38 +02:00

Pratik Borhade commented

2023-06-26 11:38:16 +02:00

Hi, probably related to other reports on AMD platforms: #109096
@iss , can you confirm?

Hi, probably related to other reports on AMD platforms: #109096 @iss , can you confirm?

Richard Antalik commented

2023-06-26 13:51:31 +02:00

I am at HQ this week, so don't have mac machine available.

👍 1

Michael Parkin-White commented

2023-06-27 12:51:09 +02:00

I believe this is caused by the same problem as resolved in this PR: #109358

would you please be able to verify whether this still occurs with the latest daily build? ( https://builder.blender.org/download/daily/ )
Thanks!

I believe this is caused by the same problem as resolved in this PR: https://projects.blender.org/blender/blender/pulls/109358 would you please be able to verify whether this still occurs with the latest daily build? ( https://builder.blender.org/download/daily/ ) Thanks!

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-06-28 05:25:04 +02:00

Matthias commented

2023-07-01 13:12:45 +02:00

@Michael-Parkin-White-Apple I've just downloaded the 3.6 release version and I'm happy to report that the issue is fixed. Thanks for the patch and for making lots of Mac/Intel/AMD Blender unsers happy again 👍