3.6.0 crashes on Mac Pro Intel with AMD GPUs on Cycles / GPU Compute (macOS Monterey) #108131

Closed
opened 2023-05-22 04:23:46 +02:00 by Caco Oportot · 11 comments

System Information
Operating system: macOS Monterey 12.6.6 (21G646), 12.6.4 (21G526)
Graphics card: AMD FirePro D500 3 GB

Mac Pro (Late 2013)
2,7 GHz 12-Core Intel Xeon E5
64 GB 1866 MHz DDR3
AMD FirePro D500 3 GB

Blender Version
Broken Since: 3.6.0, 69d52c5f1c, main, 04-29-2023 (untill newest 3.6.0 Beta)
Worked: 3.6.0, 252b0a023e, main, 04-28-2023

Short description of error

Blender crashes on render and viewport on Cycles when GPU Compute enabled.

Exact steps for others to reproduce the error

Launch Blender on default cube scene
Go to Render Properties and select Cycles and GPU Compute
Change Viewport Shading to Rendered... crash.

Same if you try to Render the scene.

Screen Shot 2023-05-21 at 22.12.45.png
Screen Shot 2023-05-21 at 22.12.06.png

Crash Report:

blender_crash_05-2023.txt

**System Information** Operating system: macOS Monterey 12.6.6 (21G646), 12.6.4 (21G526) Graphics card: AMD FirePro D500 3 GB Mac Pro (Late 2013) 2,7 GHz 12-Core Intel Xeon E5 64 GB 1866 MHz DDR3 AMD FirePro D500 3 GB **Blender Version** Broken Since: 3.6.0, 69d52c5f1c30, main, 04-29-2023 (untill newest 3.6.0 Beta) Worked: 3.6.0, 252b0a023e6c, main, 04-28-2023 **Short description of error** Blender crashes on render and viewport on Cycles when GPU Compute enabled. **Exact steps for others to reproduce the error** Launch Blender on default cube scene Go to Render Properties and select Cycles and GPU Compute Change Viewport Shading to Rendered... crash. Same if you try to Render the scene. ![Screen Shot 2023-05-21 at 22.12.45.png](/attachments/076397a9-b6b4-42ec-af17-8712df335ac9) ![Screen Shot 2023-05-21 at 22.12.06.png](/attachments/46f5c91a-40f7-40b4-94a0-631cf972c4bc) **Crash Report:** [blender_crash_05-2023.txt](/attachments/32801698-a9dd-4df2-a41f-0fd4948324af)
Caco Oportot added the
Priority
Normal
Status
Needs Triage
Type
Report
labels 2023-05-22 04:23:47 +02:00
Author

@Michael-Jones would you please take a look into this? Thank you in advance!

@Michael-Jones would you please take a look into this? Thank you in advance!
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2023-05-22 04:27:01 +02:00
Blender Bot added
Status
Needs Triage
and removed
Status
Archived
labels 2023-05-22 04:27:07 +02:00
Iliya Katushenock added the
Interest
Render & Cycles
label 2023-05-22 07:14:59 +02:00
Pratik Borhade added the
Platform
macOS
label 2023-05-22 16:00:07 +02:00

same issue with my mac setup:
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

As well as simply doing a viewport render with the Cycles engine and Metal Backend

Also when doing a viewport render of a scene (not just the cube) with cycles, It renders a black box and gives this error onscreen:
Camera Perspective
(13) Window Bench | Window.004
CommandBuffer Failed: cycles _metal_integrator_compact shadow states

same issue with my mac setup: 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 As well as simply doing a viewport render with the Cycles engine and Metal Backend Also when doing a viewport render of a scene (not just the cube) with cycles, It renders a black box and gives this error onscreen: Camera Perspective (13) Window Bench | Window.004 CommandBuffer Failed: cycles _metal_integrator_compact shadow states
Author

Reporting back:

The issue on my machine seems to have been resolved on Daily Builds 3.6.0 Beta (43fe7bec4f) and 4.0.0 Alpha (9a8fd2f1dd), both from 05-23-2023

@Ric-Lopez I suggest you try and install the latest daily builds, check if they fix your problem, and report back here.

Reporting back: The issue on my machine seems to have been resolved on Daily Builds **3.6.0 Beta (43fe7bec4fa5)** and **4.0.0 Alpha (9a8fd2f1ddb4)**, both from **05-23-2023** @Ric-Lopez I suggest you try and install the latest [daily builds](https://builder.blender.org/download/daily/), check if they fix your problem, and report back here.

Well it did fix the viewport render - works now!

the actual render still crashes the app

  • I would really like to know if it is video ram that is causing the problem, I have 8 GB on my video card - the machine has 128 GB, so that should not be an issue

And if it is the Video card, would an egpu with a 16 GB card fix the crashing?

Well it did fix the viewport render - works now! the actual render still crashes the app - I would really like to know if it is video ram that is causing the problem, I have 8 GB on my video card - the machine has 128 GB, so that should not be an issue And if it is the Video card, would an egpu with a 16 GB card fix the crashing?
Author

Well it did fix the viewport render - works now!

the actual render still crashes the app

  • I would really like to know if it is video ram that is causing the problem, I have 8 GB on my video card - the machine has 128 GB, so that should not be an issue

And if it is the Video card, would an egpu with a 16 GB card fix the crashing?

Maybe you could share the .blend file that causes your crash

> Well it did fix the viewport render - works now! > > the actual render still crashes the app > > - I would really like to know if it is video ram that is causing the problem, I have 8 GB on my video card - the machine has 128 GB, so that should not be an issue > > And if it is the Video card, would an egpu with a 16 GB card fix the crashing? Maybe you could share the .blend file that causes your crash

I think that the file I am working with (as a test file) has issues and that the problem is in the file not in Blender.

I am testing on various other files and Blender is handling them well - Unless I find a problem I can pass along I will have to say that you may have solved the isseue - Many Thanks

Ric

I think that the file I am working with (as a test file) has issues and that the problem is in the file not in Blender. I am testing on various other files and Blender is handling them well - Unless I find a problem I can pass along I will have to say that you may have solved the isseue - Many Thanks Ric
Author

I think that the file I am working with (as a test file) has issues and that the problem is in the file not in Blender.

I am testing on various other files and Blender is handling them well - Unless I find a problem I can pass along I will have to say that you may have solved the isseue - Many Thanks

Ric

Thanks to the developers that fixed what caused it!

Now there´s this new issue #108240 on latest 4.0.0 Daily Build that seems related to cycles-light-linking that causes this crash on my machine, please check if you can replicate on yours, and comment there: #108240

> I think that the file I am working with (as a test file) has issues and that the problem is in the file not in Blender. > > I am testing on various other files and Blender is handling them well - Unless I find a problem I can pass along I will have to say that you may have solved the isseue - Many Thanks > > Ric Thanks to the developers that fixed what caused it! Now there´s this new issue #108240 on latest [4.0.0 Daily Build](https://builder.blender.org/download/daily/blender-4.0.0-alpha+main.ba3f26fac58e-darwin.x86_64-release.dmg) that seems related to `cycles-light-linking` that causes this crash on my machine, please check if you can replicate on yours, and comment there: #108240
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2023-05-24 21:41:37 +02:00

Hi. Sorry to exhume an old thread, but I've had to revert to Blender 3.5 because 3.6 and 3.6.1 are totally unstable on my Mac Pro. It's a 24-core Intel machine with a single W6800X Duo MPX GPU.

The culprit appears to be largely working with the GPU in Cycles – Blender quits on saving a file, quits during rendering, and even during live rendering, seemingly at its worst when dealing with displacement. I've just switched back to 3.5.1 and am already seeing substantially better stability. What has changed between builds?

I'd be happy to help triage this if you want to get in touch. The different between the builds is quite distinct. Thanks! Steve J.

EDIT: 3.5.1 is absolutely rock solid compared to 3.6.1. What have you done!?

Hi. Sorry to exhume an old thread, but I've had to revert to Blender 3.5 because 3.6 and 3.6.1 are totally unstable on my Mac Pro. It's a 24-core Intel machine with a single W6800X Duo MPX GPU. The culprit appears to be largely working with the GPU in Cycles – Blender quits on saving a file, quits during rendering, and even during live rendering, seemingly at its worst when dealing with displacement. I've just switched back to 3.5.1 and am already seeing substantially better stability. What has changed between builds? I'd be happy to help triage this if you want to get in touch. The different between the builds is quite distinct. Thanks! Steve J. EDIT: 3.5.1 is absolutely rock solid compared to 3.6.1. What have you done!?

I continue to have many of those same problems - however, I found that if I go to the RANDER Tab => scroll down to MEMORY => be sure USE TILING is on and reduce the TILE SIZE to 512 or less, the instability goes away.

The problem for me has been the Video RAM I have is insufficient with Metal turned on in SYSTEM.

But with the MEMORY turned down, it wirks fine

I continue to have many of those same problems - however, I found that if I go to the RANDER Tab => scroll down to MEMORY => be sure USE TILING is on and reduce the TILE SIZE to 512 or less, the instability goes away. The problem for me has been the Video RAM I have is insufficient with Metal turned on in SYSTEM. But with the MEMORY turned down, it wirks fine

Hi. Well I tried reducing the memory overhead, but it's still crashing (note, I have 32GB VRAM! This shouldn't be an issue.)

I just loaded a scene in 3.5.1 and the difference is night and day. 3.5 just feels much more robust; 3.6 feels like it's always on the edge of crashing. Everything takes a split second longer to do and I get much more spinning beachball action. I'll stick with 3.5.1 for the time being, until someone can report back as to why this behaviour is happening, and how to properly fix it.

Hi. Well I tried reducing the memory overhead, but it's still crashing (note, I have 32GB VRAM! This shouldn't be an issue.) I just loaded a scene in 3.5.1 and the difference is night and day. 3.5 just feels much more robust; 3.6 feels like it's always on the edge of crashing. Everything takes a split second longer to do and I get much more spinning beachball action. I'll stick with 3.5.1 for the time being, until someone can report back as to why this behaviour is happening, and how to properly fix it.

I am not a programmer, just a user, but 32 GB ram ought to do it without changing the tile size

I know that between 3.5 and 3.6 they (with Apple) updated the Metal dependencies...

The only other suggestion I can make is not the best, but in the Preferences => System play with the settings under the topmost heading of "Cycles render devices" Leave the top "Metal" on but either uncheck your Video Card (I know there goes the GPU) or Just below that in the "GPU Backend" change it back to OpenGL.

I realize this essentially eliminates your GPU processing capability, but this and reducing tile size are the only two solutions I have been able to come up with to make the new Blender apps work on My Mac (a desktop iMac i9-10910 CPU @ 3.60GHz - not a potential screamer like yours should be)

I am not a programmer, just a user, but 32 GB ram ought to do it without changing the tile size I know that between 3.5 and 3.6 they (with Apple) updated the Metal dependencies... The only other suggestion I can make is not the best, but in the Preferences => System play with the settings under the topmost heading of "Cycles render devices" Leave the top "Metal" on but either uncheck your Video Card (I know there goes the GPU) or Just below that in the "GPU Backend" change it back to OpenGL. I realize this essentially eliminates your GPU processing capability, but this and reducing tile size are the only two solutions I have been able to come up with to make the new Blender apps work on My Mac (a desktop iMac i9-10910 CPU @ 3.60GHz - not a potential screamer like yours should be)
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#108131
No description provided.