GPU Metal Render fails with error "CommandBuffer Failed: cycles metal integrator_ reset" on M2 MacBook Air #101787

New Issue

stephen thomas · 2022-10-13T08:27:22+02:00

stephen thomas commented

2022-10-13 08:27:22 +02:00

System Information
Operating system: macOS-13.0-arm64-arm-64bit 64 Bits
Graphics card: Apple M2 Apple 4.1 Metal - 83

Blender Version
Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: b292cfe5a9
Worked: -

Short description of error
Certain scenes fail to render under GPU Metal on the M2 MacBook Air.

Exact steps for others to reproduce the error

Download The Junk Shop demo file.
Open on an M2 MacBook Air.
Click 'Edit>Preferences' and select 'System'
Check 'Apple M2 (GPU - 8 cores)' under 'Cycles Render Devices'
Close Preferences
In Render Properties, make sure:
Render Engine is 'Cycles'
Device is 'GPU Compute'
Render still image (fn f12)
After a couple of seconds, the render fails with the error "CommandBuffer Failed: cycles_metal_integrator_ reset"

The scene renders without issue if the Device in Render Properties is set to CPU.
The scene also renders without issue if 'Apple M2' is enabled and 'Apple M2 (GPU - 8 cores)' is disabled in Cycles Render Devices in Preferences.
Enabling 'MetalRT' in Preferences results in the same error.

**System Information** Operating system: macOS-13.0-arm64-arm-64bit 64 Bits Graphics card: Apple M2 Apple 4.1 Metal - 83 **Blender Version** Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: `b292cfe5a9` Worked: - **Short description of error** Certain scenes fail to render under GPU Metal on the M2 MacBook Air. **Exact steps for others to reproduce the error** - Download [The Junk Shop ](https://cloud.blender.org/p/gallery/5dd6d7044441651fa3decb56) demo file. - Open on an M2 MacBook Air. - Click 'Edit>Preferences' and select 'System' - Check 'Apple M2 (GPU - 8 cores)' under 'Cycles Render Devices' - Close Preferences - In Render Properties, make sure: - Render Engine is 'Cycles' - Device is 'GPU Compute' - Render still image (fn f12) - After a couple of seconds, the render fails with the error "CommandBuffer Failed: cycles_metal_integrator_ reset" ![Screenshot 2022-10-13 at 07.13.12.png](https://archive.blender.org/developer/F13671665/Screenshot_2022-10-13_at_07.13.12.png) The scene renders without issue if the Device in Render Properties is set to CPU. The scene also renders without issue if 'Apple M2' is enabled and 'Apple M2 (GPU - 8 cores)' is disabled in Cycles Render Devices in Preferences. Enabling 'MetalRT' in Preferences results in the same error.

stephen thomas commented

2022-10-13 08:27:22 +02:00

Added subscriber: @stephenthomas

stephen thomas commented

2022-10-13 08:56:06 +02:00

I have a M1 Mac Mini at the office that's running macOS 12, I'll try rendering on that today to see if the same issue occurs.

stephen thomas commented

2022-10-13 10:13:59 +02:00

Crashes with the same error on the mini. Details:

Mac mini (M1, 2020) - 8GB Memory

macOS 12.6

Blender 3.3.0

Crashes with the same error on the mini. Details: Mac mini (M1, 2020) - 8GB Memory macOS 12.6 Blender 3.3.0 ![Screenshot 2022-10-13 at 09.10.53.png](https://archive.blender.org/developer/F13672102/Screenshot_2022-10-13_at_09.10.53.png)

Omar Emara commented

2022-10-13 15:08:37 +02:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-10-13 15:08:37 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Omar Emara commented

2022-10-13 15:08:37 +02:00

Seems similar to #97065, #97155, and #101556.
Could this be an insufficient memory issue as mentioned in one of the reports? Does the M2 have 8 GB of memory as well? Can you monitor total memory usage during rendering and check if the crash happens at a particular point?

Seems similar to #97065, #97155, and #101556. Could this be an insufficient memory issue as mentioned in one of the reports? Does the M2 have 8 GB of memory as well? Can you monitor total memory usage during rendering and check if the crash happens at a particular point?

stephen thomas commented

2022-10-13 15:44:35 +02:00

Hey Omar,

Yes, both machines have 8GB of memory. Have just checked and it does look like it could be a memory issue, here's a screen recording of the render and activity monitor:

Screen Recording 2022-10-13 at 14.35.34.mov

Blender's memory usage peaks at 13.79GB. Although there isn't an 'insufficient memory' error like in https://developer.blender.org/T97155, I'd guess this is the issue.

Hey Omar, Yes, both machines have 8GB of memory. Have just checked and it does look like it could be a memory issue, here's a screen recording of the render and activity monitor: [Screen Recording 2022-10-13 at 14.35.34.mov](https://archive.blender.org/developer/F13673287/Screen_Recording_2022-10-13_at_14.35.34.mov) Blender's memory usage peaks at 13.79GB. Although there isn't an 'insufficient memory' error like in https://developer.blender.org/T97155, I'd guess this is the issue.

Omar Emara commented

2022-10-13 16:14:51 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Omar Emara commented

2022-10-13 16:14:51 +02:00

I can't view the above video for some reason. But as far as I can see in the code, the device should be able to tell us if it can't allocate a buffer with a System is out of GPU memory error.
But I guess it is possible that it does other unguarded allocations internally. Maybe someone with a Mac can reproduce and investigate this better.

I can't view the above video for some reason. But as far as I can see in the code, the device should be able to tell us if it can't allocate a buffer with a `System is out of GPU memory` error. But I guess it is possible that it does other unguarded allocations internally. Maybe someone with a Mac can reproduce and investigate this better.

stephen thomas commented

2022-10-13 16:20:07 +02:00

Ah, sorry it isn’t playing for you. Here’s a screenshot at the point where it crashes

No memory errors, just lots of CommandBuffer Failed errors

Ah, sorry it isn’t playing for you. Here’s a screenshot at the point where it crashes ![6A4961BC-5307-47AC-B9F6-69EF5F4C5961.jpeg](https://archive.blender.org/developer/F13673436/6A4961BC-5307-47AC-B9F6-69EF5F4C5961.jpeg) No memory errors, just lots of CommandBuffer Failed errors

Valentin commented

2022-10-13 20:13:15 +02:00

Added subscriber: @Oversun

Valentin commented

2022-10-13 20:13:15 +02:00

The same issue on MacBook Pro M1 with 16gb ram, if any blender files have exceed memory more then available ram have the same issue with CommandBuffer

The same issue on MacBook Pro M1 with 16gb ram, if any blender files have exceed memory more then available ram have the same issue with CommandBuffer ![Screenshot 2022-10-13 at 21.18.56.png](https://archive.blender.org/developer/F13674317/Screenshot_2022-10-13_at_21.18.56.png)

stephen thomas commented

2022-10-13 20:23:51 +02:00

Thanks Valentin, useful to know that it’s happening on your MBP too. It’s surprising to hear that 16GB isn’t enough to render this shot though, especially considering there’s some extra wiggle room with swap (Blender got up to just under 14GB with me).

stephen thomas commented

2022-10-13 20:27:30 +02:00

Just looking at your terminal screenshot and maybe I’m reading it wrong, but it looks like your memory usage peaks at 13.5GB? That’s quite a bit below 16GB

Valentin commented

2022-10-13 21:24:55 +02:00

Yes but other free ram is occupied by other apps and system itself, so its look like that Metal driver can't normally work when swap is active, the same issue I faced in Linux on CPU rendering with Dynamic Swap allocation, I don't think that's the same issue but similar one.

With CPU only this file is rendering as expected

Your demo file from this topic I was rendering as expected without any errors, so I think we need some Blender reference file that can occupy more than 16GB ram for example for reproduce it on 16ram Mac.

Yes but other free ram is occupied by other apps and system itself, so its look like that Metal driver can't normally work when swap is active, the same issue I faced in Linux on CPU rendering with Dynamic Swap allocation, I don't think that's the same issue but similar one. With CPU only this file is rendering as expected Your demo file from this topic I was rendering as expected without any errors, so I think we need some Blender reference file that can occupy more than 16GB ram for example for reproduce it on 16ram Mac.

stephen thomas commented

2022-10-14 11:28:17 +02:00

Your demo file from this topic I was rendering as expected without any errors, so I think we need some Blender reference file that can occupy more than 16GB ram for example for reproduce it on 16ram Mac.

Ah, I thought the screenshot you posted was from rendering the file I linked to, that's why I was confused 16GB couldn't handle it. If that's the case, it looks like it is just an issue of Blender running out of memory, bit odd that it's not throwing up an appropriate error though.

> Your demo file from this topic I was rendering as expected without any errors, so I think we need some Blender reference file that can occupy more than 16GB ram for example for reproduce it on 16ram Mac. Ah, I thought the screenshot you posted was from rendering the file I linked to, that's why I was confused 16GB couldn't handle it. If that's the case, it looks like it is just an issue of Blender running out of memory, bit odd that it's not throwing up an appropriate error though.

Richard Antalik commented

2022-10-14 18:12:22 +02:00

Added subscriber: @iss

Richard Antalik commented

2022-10-14 18:12:22 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Richard Antalik commented

2022-10-14 18:12:22 +02:00

Just a note, that crash due to running out of memory are currently not considered to be a bug. If this is not issue with available memory, such big and complex .blend files are not accepted for bug reports and should be simplified as much as possible.

Please try to simplify .blend file as much as possible and see if this is caused by particular object, or if issue comes whenever some memory limit is exceeded.

Just a note, that crash due to running out of memory are currently not considered to be a bug. If this is not issue with available memory, such big and complex .blend files are not accepted for bug reports and should be simplified as much as possible. Please try to simplify .blend file as much as possible and see if this is caused by particular object, or if issue comes whenever some memory limit is exceeded.

stephen thomas commented

2022-10-14 18:18:39 +02:00

Good thinking Richard, best to be sure. I should have some time over the weekend to experiment, will let you know how I get on.

Valentin commented

2022-10-14 23:45:11 +02:00

I think out of physical memory should not be a problem for Blender because we have a swap for this, Blender can handle this situation on CPU rendering without any problems so maybe it can work like this for Metal as well.

Valentin commented

2022-10-14 23:51:30 +02:00

I think this is not a specific object in scene because sample scene from this post described in overview is rendering without problems on 16gb ram Mac M1. So my little opinion
that is the dynamic swap allocation handling memory issue that I faced on Linux OS with Dynamic Swap allocation for CPU render when blend file have reach physical memory and kernel try to allocate dynamic swap size for Blender
and i don't know how to set on Mac a static swap size because its simple solve this issue for CPU rendering on Linux with Dynamic Swap size allocation, maybe if you know ho to do that I can try to reproduce this on my Mac. Of course
I can mistake because really don't know how its implemented under the hood.

I think this is not a specific object in scene because sample scene from this post described in overview is rendering without problems on 16gb ram Mac M1. So my little opinion that is the dynamic swap allocation handling memory issue that I faced on Linux OS with Dynamic Swap allocation for CPU render when blend file have reach physical memory and kernel try to allocate dynamic swap size for Blender and i don't know how to set on Mac a static swap size because its simple solve this issue for CPU rendering on Linux with Dynamic Swap size allocation, maybe if you know ho to do that I can try to reproduce this on my Mac. Of course I can mistake because really don't know how its implemented under the hood.

stephen thomas commented

2022-10-15 08:36:18 +02:00

I think this is not a specific object in scene because sample scene from this post described in overview is rendering without problems on 16gb ram Mac M1.

Very good point. I’ll do some poking around anyway to be sure though.

… i don't know how to set on Mac a static swap size because its simple solve this issue for CPU rendering on Linux with Dynamic Swap size allocation, maybe if you know ho to do that I can try to reproduce this on my Mac.

I don’t think macOS lets you change the swap size: https://discussions.apple.com/thread/7509515

I think out of physical memory should not be a problem for Blender because we have a swap for this, Blender can handle this situation on CPU rendering without any problems so maybe it can work like this for Metal as well.

Yes, that’s my thinking too, with unified memory and all the CPU and GPU should have access to the same pool of memory. The scene renders without issue on the CPU. The question is: Is Metal supposed to work with memory the same way independent of compute device? If so, this could be a bug. If not, it would be a feature request/improvement.

> I think this is not a specific object in scene because sample scene from this post described in overview is rendering without problems on 16gb ram Mac M1. Very good point. I’ll do some poking around anyway to be sure though. > … i don't know how to set on Mac a static swap size because its simple solve this issue for CPU rendering on Linux with Dynamic Swap size allocation, maybe if you know ho to do that I can try to reproduce this on my Mac. I don’t think macOS lets you change the swap size: https://discussions.apple.com/thread/7509515 > I think out of physical memory should not be a problem for Blender because we have a swap for this, Blender can handle this situation on CPU rendering without any problems so maybe it can work like this for Metal as well. Yes, that’s my thinking too, with unified memory and all the CPU and GPU should have access to the same pool of memory. The scene renders without issue on the CPU. The question is: Is Metal supposed to work with memory the same way independent of compute device? If so, this could be a bug. If not, it would be a feature request/improvement.

stephen thomas commented

2022-10-15 11:06:41 +02:00

I've experimented with disabling collections to see if anything in particular causes the crash, can confirm that all collections render fine individually, the crash occurs when too many are enabled at the same time (i.e. taking up too much memory). Still can't see any memory warnings in the terminal, but one of the crashes managed to write out a crash report, see below

Blender 2.crash.txt

It's a separate issue, maybe hair rendering hasn't been implemented for Metal yet, but the girls hair isn't rendering for me. If this is an error, please let me know and I'll submit a separate bug report for this. No settings were changed from the original download (except for disabling collections) and the hair renders correctly on the CPU.

I've experimented with disabling collections to see if anything in particular causes the crash, can confirm that all collections render fine individually, the crash occurs when too many are enabled at the same time (i.e. taking up too much memory). Still can't see any memory warnings in the terminal, but one of the crashes managed to write out a crash report, see below [Blender 2.crash.txt](https://archive.blender.org/developer/F13682077/Blender_2.crash.txt) It's a separate issue, maybe hair rendering hasn't been implemented for Metal yet, but the girls hair isn't rendering for me. If this is an error, please let me know and I'll submit a separate bug report for this. No settings were changed from the original download (except for disabling collections) and the hair renders correctly on the CPU. ![The Junk Shop Girl - No Hair.jpg](https://archive.blender.org/developer/F13682089/The_Junk_Shop_Girl_-_No_Hair.jpg)

Richard Antalik commented

2022-10-17 18:00:33 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Richard Antalik commented

2022-10-17 18:00:33 +02:00

Added subscribers: @Michael-Jones, @brecht

Richard Antalik commented

2022-10-17 18:00:33 +02:00

In #101787#1432639, @Oversun wrote:
I think out of physical memory should not be a problem for Blender because we have a swap for this, Blender can handle this situation on CPU rendering without any problems so maybe it can work like this for Metal as well.

Sure, Blender would likely be able to handle swapping, but I don't think Metal can work with swap. However I can't find any resources on this topic.

In #101787#1432735, @stephenthomas wrote:
I've experimented with disabling collections to see if anything in particular causes the crash, can confirm that all collections render fine individually, the crash occurs when too many are enabled at the same time (i.e. taking up too much memory). Still can't see any memory warnings in the terminal, but one of the crashes managed to write out a crash report, see below

Blender 2.crash.txt

Not familiar with Metal pipeline at all, but crash log seems to point in crash in Metal itself. So I would assume with aditional info that this happens due to insuficient physical memory. So I don't think this is a bug, but I would rather defer to @brecht or @Michael-Jones to have a look.

> In #101787#1432639, @Oversun wrote: > I think out of physical memory should not be a problem for Blender because we have a swap for this, Blender can handle this situation on CPU rendering without any problems so maybe it can work like this for Metal as well. Sure, Blender would likely be able to handle swapping, but I don't think Metal can work with swap. However I can't find any resources on this topic. > In #101787#1432735, @stephenthomas wrote: > I've experimented with disabling collections to see if anything in particular causes the crash, can confirm that all collections render fine individually, the crash occurs when too many are enabled at the same time (i.e. taking up too much memory). Still can't see any memory warnings in the terminal, but one of the crashes managed to write out a crash report, see below > > [Blender 2.crash.txt](https://archive.blender.org/developer/F13682077/Blender_2.crash.txt) Not familiar with Metal pipeline at all, but crash log seems to point in crash in Metal itself. So I would assume with aditional info that this happens due to insuficient physical memory. So I don't think this is a bug, but I would rather defer to @brecht or @Michael-Jones to have a look.

Duduche commented

2022-10-26 00:38:45 +02:00

Added subscriber: @duduchier

Duduche commented

2022-10-26 00:38:45 +02:00

Hello !

I run

a MacBook Pro M1 Max with 64 GB of RAM (!!!)
MacOS 12.6 (Monterey)
Blender version 3.3.1 (3.3.1 2022-10-05)
Cycles with GPU "experimental" option

I randomly but often get:
CommandBuffer Failed: cycles_metal_integrator_queued_paths_array

Impossible to entirely render a short animation containing atmospheric haze, 6 layers and compositing (denoise etc).

I think the rendering cannot be run again until I quit (not sure anymore).

Resizing in % the render resolution, does not solve the problem.
Changing the out file type neither.

But no crash until I ask to quit myself.
I always get the same crash log:

———————————>

Crashed Thread: 22

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x000000018f02e3ec
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5
Terminating Process: exc handler [628]

Kernel Triage:
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage

———————————
Thread 22 Crashed:
0 libsystem_c.dylib 0x18f02e3ec __abort + 160
1 libsystem_c.dylib 0x18f02e3ec __abort + 160
2 libsystem_c.dylib 0x18f02e34c abort + 180
3 libsystem_c.dylib 0x18f02d754 __assert_rtn + 272
4 Metal 0x197aeadd8 MTLReportFailure.cold.1 + 56
5 Metal 0x197ad4790 MTLReportFailure + 480
6 Metal 0x197a27178 -[_MTLCommandEncoder dealloc] + 128
7 AGXMetalG13X 0x1d5cf683c 0x1d5b14000 + 1976380
8 libobjc.A.dylib 0x18ef812b4 AutoreleasePoolPage::releaseUntil(objc_object**) + 196
9 libobjc.A.dylib 0x18ef7db34 objc_autoreleasePoolPop + 212
10 libobjc.A.dylib 0x18ef86218 AutoreleasePoolPage::tls_dealloc(void*) + 136
11 libsystem_pthread.dylib 0x18f0f1bd4 _pthread_tsd_cleanup + 524
12 libsystem_pthread.dylib 0x18f0f4968 _pthread_exit + 84
13 libsystem_pthread.dylib 0x18f0f4278 _pthread_start + 160
14 libsystem_pthread.dylib 0x18f0ef08c thread_start + 8

Hello ! I run - a MacBook Pro M1 Max with 64 GB of RAM (!!!) - MacOS 12.6 (Monterey) - Blender version 3.3.1 (3.3.1 2022-10-05) - Cycles with GPU "experimental" option I randomly but often get: CommandBuffer Failed: cycles_metal_integrator_queued_paths_array Impossible to entirely render a short animation containing atmospheric haze, 6 layers and compositing (denoise etc). I think the rendering cannot be run again until I quit (not sure anymore). Resizing in % the render resolution, does not solve the problem. Changing the out file type neither. But no crash until I ask to quit myself. I always get the same crash log: ———————————> Crashed Thread: 22 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x000000018f02e3ec Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5 Terminating Process: exc handler [628] Kernel Triage: VM - pmap_enter failed with resource shortage VM - pmap_enter failed with resource shortage ——————————— Thread 22 Crashed: 0 libsystem_c.dylib 0x18f02e3ec __abort + 160 1 libsystem_c.dylib 0x18f02e3ec __abort + 160 2 libsystem_c.dylib 0x18f02e34c abort + 180 3 libsystem_c.dylib 0x18f02d754 __assert_rtn + 272 4 Metal 0x197aeadd8 MTLReportFailure.cold.1 + 56 5 Metal 0x197ad4790 MTLReportFailure + 480 6 Metal 0x197a27178 -[_MTLCommandEncoder dealloc] + 128 7 AGXMetalG13X 0x1d5cf683c 0x1d5b14000 + 1976380 8 libobjc.A.dylib 0x18ef812b4 AutoreleasePoolPage::releaseUntil(objc_object**) + 196 9 libobjc.A.dylib 0x18ef7db34 objc_autoreleasePoolPop + 212 10 libobjc.A.dylib 0x18ef86218 AutoreleasePoolPage::tls_dealloc(void*) + 136 11 libsystem_pthread.dylib 0x18f0f1bd4 _pthread_tsd_cleanup + 524 12 libsystem_pthread.dylib 0x18f0f4968 _pthread_exit + 84 13 libsystem_pthread.dylib 0x18f0f4278 _pthread_start + 160 14 libsystem_pthread.dylib 0x18f0ef08c thread_start + 8

stephen thomas commented

2022-10-26 07:23:48 +02:00

Thanks Duduche, that’s really useful to know.

With this new information and seeing as the crash doesn’t mention memory, it seems like a low amount of memory makes this kind of crash more common rather than being the cause.

Thanks Duduche, that’s really useful to know. With this new information and seeing as the crash doesn’t mention memory, it seems like a low amount of memory makes this kind of crash more common rather than being the cause.

Duduche commented

2022-10-26 17:08:55 +02:00

Hello again,

FYI, I am not 100% sure yet but it seems that setting up the Cycles renderer with:

"features set" -> "Supported"
"Device" -> "GPU Compute"
solves the problem.

"features set" -> "GPU "experimental" may create the error and stop the rendering.
I still need to try again soon to be sure.

Hello again, FYI, I am not 100% sure yet but it seems that setting up the Cycles renderer with: - "features set" -> "Supported" - "Device" -> "GPU Compute" solves the problem. "features set" -> "GPU "experimental" may create the error and stop the rendering. I still need to try again soon to be sure.

stephen thomas commented

2022-10-28 12:09:30 +02:00

In #101787#1437602, @duduchier wrote:
Hello again,

FYI, I am not 100% sure yet but it seems that setting up the Cycles renderer with:

"features set" -> "Supported"

"Device" -> "GPU Compute"
solves the problem.

"features set" -> "GPU "experimental" may create the error and stop the rendering.
I still need to try again soon to be sure.

Unfortunately that's not the case for me.

It could be that the experimental feature set for your scene is resulting in greater memory usage, so while switching it on is causing the crash, it's not the direct cause.

> In #101787#1437602, @duduchier wrote: > Hello again, > > FYI, I am not 100% sure yet but it seems that setting up the Cycles renderer with: > - "features set" -> "Supported" > - "Device" -> "GPU Compute" > solves the problem. > > "features set" -> "GPU "experimental" may create the error and stop the rendering. > I still need to try again soon to be sure. Unfortunately that's not the case for me. ![Screenshot 2022-10-28 at 11.03.55.png](https://archive.blender.org/developer/F13789210/Screenshot_2022-10-28_at_11.03.55.png) It could be that the experimental feature set for your scene is resulting in greater memory usage, so while switching it on is causing the crash, it's not the direct cause.

Rajin Sandira commented

2022-11-01 15:06:21 +01:00

Added subscriber: @2Face

Rajin Sandira commented

2022-11-01 15:06:21 +01:00

Previously I had the same issue, I managed to get Cycles to render on

Mac OS 13
With 8Gb of RAM
Blender 3.3.1 LTS
Rendering on M1 GPU + CPU
With Experimental Feature set enabled

without a problem, but I don't know if it might work for others cus I am running a particle simulation. I managed to do this by baking the particles. The Blend file I used is attached. Christmas Tree.blend

Previously I had the same issue, I managed to get Cycles to render on > Mac OS 13 > With 8Gb of RAM > Blender 3.3.1 LTS > Rendering on M1 GPU + CPU > With Experimental Feature set enabled without a problem, but I don't know if it might work for others cus I am running a particle simulation. I managed to do this by baking the particles. The Blend file I used is attached. [Christmas Tree.blend](https://archive.blender.org/developer/F13832864/Christmas_Tree.blend)

stephen thomas commented

2022-11-02 20:14:10 +01:00

Thanks Rajin, that’s useful to hear, I’ll see if I can do a test when I’m in the office tomorrow.

Also, I had a crash with this error on a project today. Unfortunately I won’t be able to share the project file, but the project is quite light (only simple meshes and SVG artwork). The crash didn’t occur until well into the render (frame 400, starting at 1). I’ll do some testing as soon as I can and hopefully get back with some useful information.

Thanks Rajin, that’s useful to hear, I’ll see if I can do a test when I’m in the office tomorrow. Also, I had a crash with this error on a project today. Unfortunately I won’t be able to share the project file, but the project is quite light (only simple meshes and SVG artwork). The crash didn’t occur until well into the render (frame 400, starting at 1). I’ll do some testing as soon as I can and hopefully get back with some useful information.

Fellipe Oliveira commented

2022-11-14 03:30:30 +01:00

Added subscriber: @Fellipe-Oliveira

Fellipe Oliveira commented

2022-11-14 03:30:30 +01:00

I was also experiencing the same problem, I have a MacBook Pro M1 8Gb RAM. Every time I tried to render using the GPU, the same error that appears for you appears. Until I decided to optimize the render so that it doesn't use a lot of RAM, and it worked. You can reduce the tile size, this helps a lot in the optimization. Now I can render normally using the M1 GPU.

![Screenshot at Nov 13 23-23-33.png](https://archive.blender.org/developer/F13908700/Screenshot_at_Nov_13_23-23-33.png) I was also experiencing the same problem, I have a MacBook Pro M1 8Gb RAM. Every time I tried to render using the GPU, the same error that appears for you appears. Until I decided to optimize the render so that it doesn't use a lot of RAM, and it worked. You can reduce the tile size, this helps a lot in the optimization. Now I can render normally using the M1 GPU.

blender-admin commented

2022-12-07 14:28:59 +01:00

This issue was referenced by 2dc51fccb8

This issue was referenced by 2dc51fccb8387467e8a012b07ab148078e7c9e50

Michael Jones (Apple) commented

2022-12-07 14:56:33 +01:00

Changed status from 'Needs Triage' to: 'Resolved'

Michael Jones (Apple) closed this issue

2022-12-07 14:56:33 +01:00

Michael Jones (Apple) self-assigned this 2022-12-07 14:56:33 +01:00

Grigorij-Mancinskij commented

2023-07-18 02:20:52 +02:00

Hey! Blender 3.6. MBP 16 gb. Scene I've just modeled, renders fine in 3.5 version, same as viewport render view. On 3.6 stuck on loading kernels and nothing happens.. can't get back to any other viewport, blender need to be shut.. In 3.6 if i go to CPU, then it's ok, on 3.5 does't matter if its cpu or gpu.. !3.6.1 same issues.

Screenshot 2023-07-18 at 01.22.14.png

1.5 MiB

Screenshot 2023-07-18 at 01.22.26.png

80 KiB

Screenshot 2023-07-18 at 01.22.34.png

783 KiB

image.png

991 KiB

stephen thomas commented

2023-07-19 13:27:57 +02:00

Hey @Grigorij-Mancinskij, sorry to hear you're getting crashes. This bug report has been resolved and closed, it'll probably be best to create a new bug report.

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

GPU Metal Render fails with error "CommandBuffer Failed: cycles metal integrator_ reset" on M2 MacBook Air #101787