Blender 3.5.1 + Mac + Metal + Crash #106607

New Issue

and removed

2023-04-06 20:49:53 +02:00

labels 2023-04-06 18:30:54 +02:00

Ric-Lopez commented

Thanks - I will create a new file and replicate the issue here - then send it to you

Ric-Lopez commented

2023-04-06 22:05:20 +02:00

I have 3 files here

All the same scene, a free scene downloaded from CGTrader.

The scene in the folder "Blender 3.5.1 all Metal" crashed after a few minutes

...the image "3.5.1 Amount Rendered before crash.jpg" shows how much was rendered before the crash

...the image "3.5.1 Render Setup.jpg" and "3.5.1 System Prefs.jpg" show the system and render settings

------------------------------------------------

The scene in the folder "Blender 3.4.1 Metal" also has images for the system and render settings.

It rendered completely in 14 minutes - the final image is "CozyRoom-Render"

Let me know what else you might need from me.

I had to break the textures up into smaller files for upload - they apply to both scenes

Ric

The remaining texture files are in the comment that follows

###### I have 3 files here ###### All the same scene, a free scene downloaded from CGTrader. ###### The scene in the folder "Blender 3.5.1 all Metal" crashed after a few minutes ###### ...the image "3.5.1 Amount Rendered before crash.jpg" shows how much was rendered before the crash ###### ...the image "3.5.1 Render Setup.jpg" and "3.5.1 System Prefs.jpg" show the system and render settings ###### ------------------------------------------------ ###### The scene in the folder "Blender 3.4.1 Metal" also has images for the system and render settings. ###### It rendered completely in 14 minutes - the final image is "CozyRoom-Render" ###### Let me know what else you might need from me. ***I had to break the textures up into smaller files for upload - they apply to both scenes*** ###### ###### Ric ###### ### The remaining texture files are in the comment that follows

Blender 3.5.1 all Metal.zip

46 MiB

CozyRoom-Render.tif.zip

72 MiB

textures-02.zip

90 MiB

Blender 3.4.1 Metal.zip

46 MiB

textures-01.zip

90 MiB

Ric-Lopez commented

2023-04-06 22:07:39 +02:00

Here are the remaining texture files

#### Here are the remaining texture files

textures-06.zip

22 MiB

textures-03.zip

63 MiB

textures-04.zip

36 MiB

textures-05.zip

40 MiB

Germano Cavalcante added

and removed

2023-04-06 22:12:34 +02:00

labels 2023-04-06 22:10:32 +02:00

Germano Cavalcante commented

Thanks for the file. Now I can only test it on Monday. Someone else can confirm in the mean time

Germano Cavalcante commented

2023-04-12 21:01:22 +02:00

Thanks for the files, but I can't replicate the problem and unfortunately the scenario described is too time consuming for us to track down, we require the bug reporter to narrow down the problem.

Looking at the hardware, it is possible that this problem is related to the same one described in #106551 (Blender on Mac freezes when working on shader nodes).

As the file is complex, maybe it's worth waiting for this other issue to be fixed before testing again.

System Information
Operating system: macOS-13.2.1-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M1 1.2

Thanks for the files, but I can't replicate the problem and unfortunately the scenario described is too time consuming for us to track down, we require the bug reporter to narrow down the problem. Looking at the hardware, it is possible that this problem is related to the same one described in #106551 (Blender on Mac freezes when working on shader nodes). As the file is complex, maybe it's worth waiting for this other issue to be fixed before testing again. --- **System Information** Operating system: macOS-13.2.1-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M1 1.2

Germano Cavalcante added

and removed

2023-04-12 21:37:00 +02:00

labels 2023-04-12 21:01:40 +02:00

Ric-Lopez commented

Germano
Thanks, I will try to render the file referenced in #106551 - just to see what happens, as well as my own with the latest builds.

In your opinion, do you think that this an AMD issue? And would a newer AMD card (as an eGPU) help?

Germano Thanks, I will try to render the file referenced in #106551 - just to see what happens, as well as my own with the latest builds. In your opinion, do you think that this an AMD issue? And would a newer AMD card (as an eGPU) help?

Ric-Lopez commented

2023-04-13 00:16:00 +02:00

Tried the new Blender build with the file I sent (above) and Blender with Metal enabled and GPU Metal backend on and it still crashes partway throough a render (single frame render)

I tried the file referenced #106551 and have no trouble maneuvering through that file or even rendering it.

### How do I get you a bug report?

Tried the new Blender build with the file I sent (above) and Blender with Metal enabled and GPU Metal backend on and it still crashes partway throough a render (single frame render) I tried the file referenced #106551 and have no trouble maneuvering through that file or even rendering it. _**### How do I get you a bug report?**_

Ric-Lopez commented

2023-04-13 02:00:27 +02:00

In preliminary tests, it appears that I may have a solution.

In the "preferences" => "Cycles Render Devices" => "Matal Tab", I had "AMD Radeon Pro 5500 XT" selected AND "Intel Core 19-10910 CPU @ 3.60GHz" selected as well.

When I unchecked the "Intel Core...CPU" and rendered, there was NO Crash.

I thought I had to have them both selected to have a CPU and GPU available to the Application.

I guess not!

In preliminary tests, it appears that I may have a solution. In the "preferences" => "Cycles Render Devices" => "Matal Tab", I had "AMD Radeon Pro 5500 XT" selected AND "Intel Core 19-10910 CPU @ 3.60GHz" selected as well. When I unchecked the "Intel Core...CPU" and rendered, there was NO Crash. I thought I had to have them both selected to have a CPU and GPU available to the Application. I guess not!

Metal Prefs.jpg

52 KiB

Germano Cavalcante commented

2023-04-13 15:57:18 +02:00

I'm not sure if another GPU from AMD will solve the problem.
Since the issue only occurs with mixed CPU + GPU rendering, it is possible that this is a memory issue (that the hardware has reached the limits of available RAM). In these cases GPUs with More VRAM can help.

But that doesn't explain why the same file works in 3.4.1 and not in 3.5.1

In addition to #106551, there is another issue related to AMD GPUs that is being investigated. See #106657

I'm not sure if another GPU from AMD will solve the problem. Since the issue only occurs with mixed CPU + GPU rendering, it is possible that this is a memory issue (that the hardware has reached the limits of available RAM). In these cases GPUs with More VRAM can help. But that doesn't explain why the same file works in 3.4.1 and not in 3.5.1 In addition to #106551, there is another issue related to AMD GPUs that is being investigated. See #106657

Ric-Lopez commented

2023-04-13 17:06:10 +02:00

I image these are AMD issues, but I could not reproduce the issue cited in #106657
on my Intel Mac

iMac (Retina 5K, 27-inch, 2020)
3.6 GHz 10-Core Intel Core i9
128 GB 2667 MHz DDR4
AMD Radeon Pro 5500 XT 8 GB

I image these are AMD issues, but I could not reproduce the issue cited in #106657 on my Intel Mac iMac (Retina 5K, 27-inch, 2020) 3.6 GHz 10-Core Intel Core i9 128 GB 2667 MHz DDR4 AMD Radeon Pro 5500 XT 8 GB

Germano Cavalcante commented

2023-04-13 17:40:01 +02:00

Did you check if you also enabled the Intel CPU to render in blender 3.4.1?

Unless this is a regression, memory issues due to very complex scenes are not currently considered a bug.

Developers try to improve Blender to handle these cases of system running out of memory gracefully with error messages or something like that, but these cases are not always caught.

Did you check if you also enabled the Intel CPU to render in blender 3.4.1? Unless this is a regression, memory issues due to very complex scenes are not currently considered a bug. Developers try to improve Blender to handle these cases of system running out of memory gracefully with error messages or something like that, but these cases are not always caught.

Ric-Lopez commented

2023-04-13 19:41:14 +02:00

Yes, I have always - up til now, had both check boxes checked -

Screen Shot 2023-04-13 at 1.40.47 PM.jpg

36 KiB

Ric-Lopez commented

2023-04-23 21:29:47 +02:00

Germano - am I the only one with this issue?
It remains an issue even in today's build in the sample file "Victor" even with AMD Radeon..." Turned On and "Intel Core...CPU" turned off and Metal Checked.

My computer has plenty of RAM 128 GB - But the AMD video card has only 8 GB - How can I determine if the issue is video RAM? There is no feedback from Blender as to the issue.

This is becomming very frustrating - Blender 3.4.1 still works without crashing.

I it just a matter of AMD updating Drivers?

Germano - am I the only one with this issue? It remains an issue even in today's build in the sample file "Victor" even with AMD Radeon..." Turned On and "Intel Core...CPU" turned off and Metal Checked. My computer has plenty of RAM 128 GB - But the AMD video card has only 8 GB - How can I determine if the issue is video RAM? There is no feedback from Blender as to the issue. This is becomming very frustrating - Blender 3.4.1 still works without crashing. I it just a matter of AMD updating Drivers?

Germano Cavalcante commented

2023-04-24 15:44:49 +02:00

I tested it once, but as the file is so complex and takes a long time to render, I'm holding back from testing it again.

This report seems to fall under the "Too complex file report, where user could not simplify enough" scenario from Triaging_Playbook.

It also appears to be an "out of memory" issue (often not considered a bug unless it's a regression).

Recently there have been some improvements made to how Metal handles memory when rendering with Eevee, I'm not sure if this affects Cycles, but we can see that development in this area.

Have you checked if, by any chance, you enabled MetalRT in 3.5?

I tested it once, but as the file is so complex and takes a long time to render, I'm holding back from testing it again. This report seems to fall under the "Too complex file report, where user could not simplify enough" scenario from [Triaging_Playbook](https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook). It also appears to be an "out of memory" issue (often not considered a bug unless it's a regression). Recently there have been some improvements made to how Metal handles memory when rendering with Eevee, I'm not sure if this affects Cycles, but we can see that development in this area. Have you checked if, by any chance, you enabled MetalRT in 3.5?

Germano Cavalcante added

and removed