Cycles render doesn't work on Intel Mac #120126
Labels
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
10 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#120126
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Intel iMac 2019, 27 inches
Operating system: macOS Sonoma 14.3.1
Graphics card: Radeon Pro 570X 4 GB
Blender Version
Broken: 4.1
Worked: 4.0.2
Short description of error**
Any render operation using Cycles with GPU Compute crashes Blender and quits. It works with Cycles using CPU or EEVEE.
Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).
Just assign a material to the cube (I subdivided and smoothed it, but it crashes also without any modification ) and render an image. The program quits immediately.
Hi, thanks for the report. Could you attach crash logs?: https://docs.blender.org/manual/en/dev/troubleshooting/crash.html#macos
Hi. Of course. I've just generated a new log, I'm attaching it. Hope it helps.
Thanks.
Alex.-
Thanks. From call stack of main-thread, crash seems to occur in
MEM_lockfree_mallocNwhen allocating memory.Could you attach file in case any particular property is enabled in file that triggered the crash?
@iss @Alaska can you reproduce on mac?
I am personally unable to reproduce a crash following these steps:
Sadly I don't really know any further questions to ask that might help in identifying the cause.
System Information
Operating system: macOS-14.2.1-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M1 Pro 1.2
Blender version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash:
40a5e739e270I also had the same problem as this ——
（Any render operation using Cycles with GPU Compute crashes Blender and quits. It works with Cycles using CPU or EEVEE）
When I switch back to the solid view, Blender becomes unresponsive and can only be forced to exit without any crash log.
I upload a screenshot, Hope it helps.
Thanks.
My Blender Version
Broken: 4.1
Worked: 4.0.1
System Information
Intel iMac 2020, 27 inches
Operating system: macOS Monterey 12.5.1
Graphics card: AMD Radeon Pro 5500 XT 8 GB
There's no special parameters/properties used to reproduce the problem. Just take the default cube, assign any material and try to render with Cycles. This works perfectly on 4.0.x
Maybe this is my specific hardware with this particular version of Blender that causes the problem?
Attached is my iMac configuration AND a small video where I've recorded the issue.
Questions/Comments:
The fact that I have different versions of Blender installed, could have any effect on the render?
As you can see, as soon as I select Render Image from the menu, it crashes. Same happens when I choose Cycles in Layout mode AND GPU.
Everything runs normally if I choose CPU for Cycles render.
Thanks.
Alex.-
You have a different hardware. Probably it has something to do.
Thanks,
Alex.-
AMD GPU via Metal support has been a bit of a mess lately, and support for AMD GPUs on macOS in Cycles may be removed in the near future as a result of it.
My comment was just to confirm that the issue isn't present on Apple Silicon, and I'm not sure what questions to ask to help with identifying the cause, because the causes for these AMD GPU on macOS issues are usually compiler issues, which are hard to track down.
I understand. I just wanted to make all information I have available, just in case there's a fix. My iMac is 2019, It would be sad if I won't be able to use new Blender versions due to this issue. Thanks anyway.
I'm having what looks like the same issue. Please reference report blender#120183. When I start Blender in Terminal, I get this error:
FunctionPointer is not supported on this hardware. Please check the supportsFunctionPointers or supportsRayTracing flag before using it
zsh: illegal hardware instruction ./Blender
The crash report says that it was trying to execute a bad instruction. works perfect in 4.0.2.. Fails in everything after 4.1.
Hi. I'd never tried it from the command line. You gave me the idea, will try right now. It's possible I could get more information about the problem. Thanks!
You can also send your Blender crash report using the Console app in the utilities folder. My crash included this info:
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4
Terminating Process: exc handler [22421]
It would be interesting if yours is the same.
Hi Fred. I did send the crash already, at the top of this report as by Pratik Borhade request. Here's the output after starting Blender from the command line:
alex@alexiMac MacOS % ./Blender
Read prefs: "/Users/alex/Library/Application Support/Blender/4.1/config/userpref.blend"
GoB Found System: Darwin
use zsh
FunctionPointer is not supported on this hardware. Please check the supportsFunctionPointers or supportsRayTracing flag before using it
zsh: illegal hardware instruction ./Blender
Looks like it's the same message you received.
I also checked in /Users/alex/Library/Application Support/Blender/4.1/config/platform_support.txt file.
It reads:
alex@alexiMac config % more platform_support.txt
{AMD Radeon Pro 570X/Metal API/1.2}=SUPPORTED
It's supposed to work, right?
Alex.-
By the way: it looks like it's the same error...:
"exception" : {"codes":"0x0000000000000001, 0x0000000000000000","rawCodes":[1,0],"type":"EXC_BAD_INSTRUCTION",
"signal":"SIGILL"},
"termination" : {"flags":0,"code":4,"namespace":"SIGNAL","indicator":"Illegal instruction: 4","byProc":"exc ha
ndler","byPid":35213},
The GPU appears to be supported but FunctionPointer nor RayTracing are supported. This is according to a Mac app called GLview-MacOS. This app is available from the App Store and according to it, neither are supported on my Mac at least. Apparently Blender 4.1 thinks one or both are. That would probably do it!
I wonder why Cycles worked in up to 4.0.2 and not on 4.1. The changes were on Blender then code, right?
Can you try setting the environment variable
OIDN_DEVICE_METAL=0before starting blender ?That appears to be the problem. I'm just guessing but the error "FunctionPointer is not supported on this hardware" is valid. It's not supported on my Mac. It's also not supported with 4.0.2 but Blender still works! Sounds like a coding error in Blender 4.1 and later.
But...
I can try it on my machine. Can you give me the full command line please.
not a mac user, so high probability i'm wrong, but try
export OIDN_DEVICE_METAL=0and then start blender from that same console
I did it and then made sure it was set, and it was. I then started Blender from the Terminal and got the same error as before when I tried to render with the GPU:
FunctionPointer is not supported on this hardware. Please check the supportsFunctionPointers or supportsRayTracing flag before using it
zsh: illegal hardware instruction ./Blender
FYI: As far as I can determine using a utility, Both FunctionPointer and RayTracing are not supported on my GPU. But Blender 4.0.2 runs perfect.
Same result here. Didn't work. Everything seems to indicate that I'll continue using 4.0.x until this is fixed.
Is someone that's having this issue able to test Blender 4.1 Alpha/Beta versions to help identify when this issue was introduced?
Blender 4.1 Alpha/Beta can be downloaded from here: https://builder.blender.org/download/daily/archive/
Please test a wide range of versions and report back with the newest version that works and the oldest version that doesn't work.
given the crash is inside oidn, i'm gonna assume it'll be one of the oidn updates.
Ah, I missed that. Setting back to "Needs Triage"
Hi, I did try current 4.1.1 RC and 4.2 Alpha, both exhibit same behaviour . Blender crashes immediately when trigerring anything GPU related on a 580X in 2019 iMac , everything was fine until 4.0.2.
4.1Intel version (and ARM for that matter) does run fine on my work Studio.
Oddly enough my work colleague has a 2019 Mac Pro with a AMD Pro 580X 8GB (system info attached) and it works just fine.
I dont know if its relevant or not but I do remember I've had issues with crashing on some renders in the past using LuxCore, someone more knowledgeable than me looked at my iMac clinfo and told me my problems were because although the GPU has 8GB the Apple drivers were 32bits and could only adress 4GB , no idea if its related.
EDIT: Also tried 4.1 on a 2013 MacPro with dual FirePro D300 2GB and it works "just fine".
EDIT2: 4.1 also works fine on a 2019 iMac with a 570X 4 GB
So 4.0.2 was the first version to have issues? And when you say crashes occur when doing anything GPU related, this sounds very different from the issue experienced here, which is only when rendering with the GPU in Cycles. So you'll probably want to create a seperate bug report for your issue.
It would also be good to know your systems information so we can compare it against your college one to help identify the differences that could be causing issues.
Sry, I dont use or ever used Eevee, my bad.Should rephrase: Anything GPU related meant trigerring a render or switching to rendered viewport (in Cycles).I didnt wanna "spam" , my system report in on the reference (closed) thread, but I'll attach here as well.
The first to have an issue was 4.1
4.0.2 works ok.
EDIT:Attached clinfo for both machines, might help spot differences? Dont mind running any other steps that could help triage.
Got one more piece of information: The previous iMac with a 570X that was working ok with 4.1 was running on Monterey 12.6 . I updated it to Sonoma 14.4.1 and suddenly stopped working.Same symptoms as my own iMac: crashes on using GPU in Cycles.
MacPro 580x is on Ventura 13.6 but since its a work computer cant take the chance to upgrade.
So,looks like Apple is at fault here, and somehow messed drivers in Sonoma , no sure how to proceed.
I followed your request and found that the last version that did not crash was Blender Beta 4.1.0 released on February 8th commit
4a50f1d4ee. It included Eevee-Next, did not crash, but did not render properly either. The render result was a blank page.The first version to crash was Blender Beta 4.1.0 released on February 9th (commit
2e6223d90f). It did not include Eevee-Next and crashed immediately. Let me know if there is anything else you need.Hi. I've skipped 4.1.1 Alpha and tested 4.2 Alpha . Same problem with Cycles. I assume that the same code used for 4.1 is still on 4.2.
By the way, I tested 4.1 and 4.2 on Windows, just to make sure this is definitely related to macOS/Apple hardware. It worked fine.
Obviously it's a graphic card coding issue.
Some code changed in the move from 4.0.x to 4.1
I have a notification from Apple updates, telling that Sonoma 14.4.1 is available. I'm on 14.3.1. I will update my macOS and see if something changes. Not many expectations, since MCurto tried it already...anyway.
EDIT: Sorry, I didn't see the comment telling that it worked on Monterey.
I get what your asking, so I took the time and tested on my Sonoma 14.4.1 iMac 2019 580X (the problematic one):
Blender 4.2.0 Alpha
74b8f99b43From 08 Feb 17.12 -> Doesnt CrashBlender 4.2.0 Alpha
ca259f751d09 Feb 02:21 -> Crashes , all versions (that I tested) subsequently crash.Hope it helps.
EDIT:Same dates for 4.1 Beta:
Blender 4.1.0 Beta
4a50f1d4ee08 Feb 02:08 -> Doesnt CrashBlender 4.1.0 Beta
2e6223d90f09 Feb 01:46 - > CrashesI lack the time now but during weekend still gonna try to revert to Ventura and test , I believe the problem only shows on Sonoma AMD Metal drivers.
The testing done by @MCurto points to
898187cfabbeing the culprit commit. Which is odd, as this commit was required to fix issues introduced with Blender 4.0.2 on I believe Vega, RDNA1, and RDNA2 GPUs?The extra information provided by the other users that the crashing doesn't occur on older macOS versions is helpful. Let's see if it exposes anything in the code that might help with solving this issue.
Cycles has some code in it's Metal implementation that is different depending on your OS version. Here is the list of code pieces that change in Cycles Metal when @MCurto updated their mac from macOS 12.6 to 14.X:
Plus a few other changes that only impact Intel GPUs or Apple Silicon GPUs.
I'll create some pull requests to test point 1 and 2.
Are the people experiencing crashes on Intel macs with AMD GPUs able to test these versions of Blender and report back on if they help or not?
https://builder.blender.org/download/patch/PR120279/
https://builder.blender.org/download/patch/PR120281/
I dont have the 580X until later in the day , long work day ahead , but did a brief test on 570X iMac Sonoma 14.4.1
EDIT:SRY Made a mess with version numbers.restesting everything.
Will try it properly later in the day on my own iMac 580X.
I was trying to delete the cached kenerls to start blank between versions, I was under the impression they should be stores in .caches under user home folder but cant seem to locate it, not sure if its a Sonoma thing
So sry for the mixup, I rechecked everything and version numbers:
https://builder.blender.org/download/patch/PR120279/ -> Crashes when triggering GPU
(Same message in terminal as already reported here)
https://builder.blender.org/download/patch/PR120281/ -> Doesnt crash but default square scene render is blacked out on GPU ,
I will test further and report at the end of the day.
Thanks for the test @MCurto . It seems like Metal-RT is enabled by default on all AMD GPUs running macOS 14 or newer. Which appears to be causing some sort of issue here on older hardware. I have created a pull request that will fix this issue: !120299
Even with the fix, you are experiencing issues (the render is black). This is likely the same issue reported here: #120046 , which is specific to Blender 4.2
Hopefully with !120299 applied on top of 4.1, you will have a functional version of Blender 4.1.X (and I'll see if I can get a build for you to test). As for the black rendering issues in 4.2, that will need to be addressed separately, if it's addressed at all.
I will test as soon as possible.
Same results here.
Outstanding.Tks for the help.So the "fix" will hopefully be on a near future daily build? Maybe a near future 4.1.1 RC?
But that confirms my tough: some weird Metal drivers change then, I truly hope Apple did that accidentally and not part of a planned obsolescence to discard users still on Intel/AMD , ultimately Blender didnt need a fix if Apple did their job right.
I guess this kind of issues will become more frequent going forward and Blender on Intel Macs have the days numbered, pretty sad considering I can still run 4.1 on a 2013 MacPro.
Assuming what I discovered is the issue, it's not that.
Cycles enables new features in Metal depending on the macOS version. This is because some features are only available in new versions of macOS. One of those features is Metal-RT (specifically Hair Metal-RT that was only added in macOS 14).
If you are using macOS 14 or newer, Cycles will check to see if your GPU supports Metal-RT, and enabled it if you're not using a M1 or M2 GPU. The aim of this code was to enable the feature on M3 and newer GPUs, but it has the side effect of enabling the feature on AMD GPUs, and some of these GPUs don't support it.
This was just an oversight in the Cycles code, and I've created a pull request to fix it. Hopefully it will be in 4.1.1 and hopefully it's the only issue 4.1.X has on AMD GPUs.
Is there any chance that we can get a patched copy to test?
Hi all.
Sorry I could just make the testing: at this time. Here are my results:
PR120279 : same problem, crashes and quits Blender
PR120281 : didn't crash and opens the render windows but shows part of the cube at the beginning and then becomes black. (This is when I select Render image from the top menu). If I render the cube in the Layout mode using Cycles, it just shows the object in black (as well as the whole floor...) Please, see attached images.On the other hand, EEVEE works normally but EEVEE Next shows only the cube in black.
Just to recall, my hardware is: iMac 27 Intel Core i5, 6 core, 64 GB memory, Graphic card: Radeon Pro 570X 4Gb.
I'm using macOS Sonoma 14.4.1
Alex.-
Here's a Blender 4.1 based version of !120299 for you to test. Please let me know if it fixes the crashing issue, and if it has the black rendering issues? 4.1 based PR120299.zip
This version is compiled by me rather than the Blender foundation. So it may appear as "untrusted" by macOS. If you feel uncomfortable because of that, then that's fine, don't use it. !120299 will likely be merged into Blender 4.1.X in the near future and you'll be able to test it in a build from the Blender foundation soon.
Please make a seperate bug report for each seperate issue. In this case it means making a seperate bug report for the EEVEE-Next issue.
All render modes work perfect for me.
Just finished more renders and so far everything is working as expected!!
Intel version has resolved issues for me (renders now works OK and no longer crashes when editing material properties).
#120203
Alaska referenced this issue2024-04-07 01:56:55 +02:00
A quick question for everyone trying 4.1 based PR120299.zip
How is Cycles rendering performance/render times? How does it compare to 4.0?
There are a bunch of scenes you can download from https://www.blender.org/download/demo-files/ if you need something to test with.
Junkshop is a nice one to use for testing: https://cloud.blender.org/p/gallery/5dd6d7044441651fa3decb56
@Alaska: 4.1 based PR120299.zip resolves the black render/preview issue on my system #120046
But with both these, I am still getting black render/preview on Cycles/GPU Compute:
https://builder.blender.org/download/patch/PR120279/
https://builder.blender.org/download/patch/PR120281/
I ran a couple of renders on both Blender versions. Here are my results:
Classroom blend file:
Blender 4.0.2 (3:15.79)
Blender 4.1.patch (3:19.12)
Barbershop blend file:
Blender 4.0.2. (14:46.70)
Blender 4.1.patch (14:41.45)
Pretty close!
I've landed a fix from Alaska to the main branch, and the fix should be included into 4.1.1.
Unfortunately, I can not fully confirm the fix on the current main branch, as the render result is just black, no matter whether HW RT is enabled or not. There is still some issue to be fixed there. It might be something unrelated to the root cause of this issue, but I am not fully confident of considering this report fully resolved before we have confirmation that fix will also work for 4.2.
Hi. I've tested PR120299 right now....Both, preview and Render Image work as expected on my iMac (Intel, i5, 2019, Sonoma 14.4.1)using Cycles GPU Complete.
I'm not sure about the performance...I should compare the same model render with 4.0.2.
According to tests done by various users, !120299 fixes the crashing issue reported here. !120299 has now been merged into Blender 4.2, and as per the general bug tracker policy, I will be closing this report as the issue has been resolved.
!120299 has also been backported to Blender 4.1.1 and you will be able to download it soon.
Although the crashing has been fixed, there are still other issues that need sorting. For example renders in Blender 4.2 seem to be black for most/all AMD GPU macOS users. This will need to be resolved seperate. For discussion about that issue, please discuss it here: #120046
Blender 4.1.1 release candidate with the fix can be downloaded from here: https://builder.blender.org/download/daily/
If you encounter any new bugs, feel free to report them.
The full official release for Blender 4.1.1 will likely happen next week.