Mac crash with cycles and any mesh (T 78581 revisited with new video card) #78793

Closed
opened 2020-07-10 14:19:30 +02:00 by Christopher Hartley · 57 comments

System Information
Operating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits
Graphics card: NVIDIA GeForce GTX 980 Ti OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.137

Blender Version
Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-07-09 17:04, hash: 3623db7784
Worked: (newest version of Blender that worked as expected)

Short description of error
I reported a similar problem (#78581) and my report was deleted because the video card was outdated (ATI Radeon HD5770 )
I upgraded the video card to an Nvidia GTX 980 Ti but get the same result.
Any attempt to view on screen with Cycles and a mesh in the model causes instant crash.
The replacement video card comes within the list of supported video cards.
It works fine in 2.83 and is recognised as a CUDA enabled GPU.
It is NOT recognised as a CUDA enabled GPU in 2.9, however.
Is the list of supported cards changing and out of date?

prefs screens.png

Exact steps for others to reproduce the error
Open a new document add a mesh attempt to switch the viewport shading to Cycles... crash every time

Thanks for looking at this... Chris

**System Information** Operating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits Graphics card: NVIDIA GeForce GTX 980 Ti OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.137 **Blender Version** Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-07-09 17:04, hash: `3623db7784` Worked: (newest version of Blender that worked as expected) **Short description of error** I reported a similar problem (#78581) and my report was deleted because the video card was outdated (ATI Radeon HD5770 ) I upgraded the video card to an Nvidia GTX 980 Ti but get the same result. Any attempt to view on screen with Cycles and a mesh in the model causes instant crash. The replacement video card comes within the list of supported video cards. It works fine in 2.83 and is recognised as a CUDA enabled GPU. It is NOT recognised as a CUDA enabled GPU in 2.9, however. Is the list of supported cards changing and out of date? ![prefs screens.png](https://archive.blender.org/developer/F8683620/prefs_screens.png) **Exact steps for others to reproduce the error** Open a new document add a mesh attempt to switch the viewport shading to Cycles... crash every time Thanks for looking at this... Chris

Added subscriber: @chrishartley

Added subscriber: @chrishartley

#80576 was marked as duplicate of this issue

#80576 was marked as duplicate of this issue

#80469 was marked as duplicate of this issue

#80469 was marked as duplicate of this issue

#80445 was marked as duplicate of this issue

#80445 was marked as duplicate of this issue

#80315 was marked as duplicate of this issue

#80315 was marked as duplicate of this issue

Added subscriber: @rjg

Added subscriber: @rjg

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

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

The NVIDIA GeForce GTX 980 Ti is a supported graphics card. Since you're still using macOS High Sierra (10.13.x) / Darwin-17.7.0 the driver is quite old, but I'm not aware of any changes that would stop it from being recognized on purpose, therefore this looks like a regression. (see comment by Brecht below)

Assuming the Blender 2.90 is installed to /Applications/Blender.app/Contents/MacOS/Blender, could you please open a terminal and run the following command to create a debug log in your home directory:

/Applications/Blender.app/Contents/MacOS/Blender --debug --debug-gpu > ~/blender_debug_output.txt 2>&1

Please try to make Blender crash again and attach the file to your bug report, as well as the crash log that macOS should create.

~~The NVIDIA GeForce GTX 980 Ti is a supported graphics card. Since you're still using macOS High Sierra (10.13.x) / Darwin-17.7.0 the driver is quite old, but I'm not aware of any changes that would stop it from being recognized on purpose, therefore this looks like a regression.~~ (see comment by Brecht below) Assuming the Blender 2.90 is installed to `/Applications/Blender.app/Contents/MacOS/Blender`, could you please open a terminal and run the following command to create a debug log in your home directory: `/Applications/Blender.app/Contents/MacOS/Blender --debug --debug-gpu > ~/blender_debug_output.txt 2>&1` Please try to make Blender crash again and attach the file to your bug report, as well as the crash log that macOS should create.

Added subscriber: @brecht

Added subscriber: @brecht

Regarding 2.90:
https://wiki.blender.org/wiki/Reference/Release_Notes/2.90/Cycles#GPU_Rendering

NVIDIA GPU rendering on macOS is no longer supported. Apple dropped support for CUDA drivers in macOS 10.14.

Regarding 2.90: https://wiki.blender.org/wiki/Reference/Release_Notes/2.90/Cycles#GPU_Rendering > NVIDIA GPU rendering on macOS is no longer supported. Apple dropped support for CUDA drivers in macOS 10.14.

This comment was removed by @rjg

*This comment was removed by @rjg*

Not for CUDA rendering with Blender 2.90, that was dropped entirely.

Not for CUDA rendering with Blender 2.90, that was dropped entirely.

@brecht Never mind, I was unaware that Blender dropped the CUDA support for all macOS versions in 2.90 due to Apple/Nvidia discontinuing the support for CUDA.

@brecht Never mind, I was unaware that Blender dropped the CUDA support for all macOS versions in 2.90 due to Apple/Nvidia discontinuing the support for CUDA.

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

Changed status from 'Needs User Info' to: 'Archived'
Robert Guetzkow self-assigned this 2020-07-10 17:26:47 +02:00

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

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

The crash is still unexplained though.

The crash is still unexplained though.
Robert Guetzkow removed their assignment 2020-07-10 18:02:08 +02:00

@chrishartley While CUDA is no longer supported, could you please still run the command described in my first comment. This would help us identify the source of the crash.

@chrishartley While CUDA is no longer supported, could you please still run the command described in my first comment. This would help us identify the source of the crash.

Crash report- #78793.rtf

Blender_2020-07-10-200114_NewMacPro.crash

As requested, I ran the debug script and have attached the bug report and the crash report.

I have to say I'm not thrilled to have just spent $600+ upgrading my video card only to be told you are now going to deprecate that, too!
The only need for the card was to be able to continue using blender past the 2.8x series.
You need to get this sort of info out there more quickly. The supported equipment list says that much older cards than mine are supported so I thought I was safe with this one.
...Chris

[Crash report- #78793.rtf](https://archive.blender.org/developer/F8684448/Crash_report-_T78793.rtf) [Blender_2020-07-10-200114_NewMacPro.crash](https://archive.blender.org/developer/F8684449/Blender_2020-07-10-200114_NewMacPro.crash) As requested, I ran the debug script and have attached the bug report and the crash report. I have to say I'm not thrilled to have just spent $600+ upgrading my video card only to be told you are now going to deprecate that, too! The only need for the card was to be able to continue using blender past the 2.8x series. You need to get this sort of info out there more quickly. The supported equipment list says that much older cards than mine are supported so I thought I was safe with this one. ...Chris

Added subscriber: @Blendify

Added subscriber: @Blendify

@chrishartley The situation with GPU rendering on macOS is unfortunately a bit complicated. Apple has deprecated their OpenCL compiler. Additionally they stopped using Nvidia GPUs in their products, which likely contributed to Nvidia's decision that CUDA-Toolkit 10.2 would be the last toolkit version to support macOS. This was announced in November 2019. I understand your frustration and indeed this could have been communicated better in Blender's roadmap for the development on macOS. Please note that Nvidia GPUs are still officially supported for running Blender, this "only" affects GPU rendering with Cycles.

The two workarounds I can think of at the moment is either a custom build with CUDA support (not sure if that is still possible) or using Boot Camp to run Windows on your Mac.

@brecht This practically means no Cycles GPU rendering support for Blender 2.90 on any macOS version. Is there anything we can tell users other than to wait for Metal/Vulkan support? Can technically experienced users on macOS prior to 10.15 still build Blender with CUDA support?

@Blendify The GPU docs for 2.90 need to fixed , CUDA is still listed as supported on macOS.

@chrishartley The situation with GPU rendering on macOS is unfortunately a bit complicated. Apple has deprecated their OpenCL compiler. Additionally they stopped using Nvidia GPUs in their products, which likely contributed to Nvidia's decision that CUDA-Toolkit 10.2 would be the last toolkit version to support macOS. This was announced in November 2019. I understand your frustration and indeed this could have been communicated better in Blender's roadmap for the development on macOS. Please note that Nvidia GPUs are still officially supported for running Blender, this "only" affects GPU rendering with Cycles. The two workarounds I can think of at the moment is either a custom build with CUDA support (not sure if that is still possible) or using Boot Camp to run Windows on your Mac. @brecht This practically means no Cycles GPU rendering support for Blender 2.90 on any macOS version. Is there anything we can tell users other than to wait for Metal/Vulkan support? Can technically experienced users on macOS prior to 10.15 still build Blender with CUDA support? @Blendify The [GPU docs for 2.90 need to fixed ](https://docs.blender.org/manual/en/dev/render/cycles/gpu_rendering.html#supported-hardware), CUDA is still listed as supported on macOS.

Crash log looks like an issue with Embree and/or TBB.

Crash log looks like an issue with Embree and/or TBB.

So despite CUDA not being available for my GPU in 2.9 it SHOULD still run on my Mac?
The crash I get with Cycles and a mesh in a document is a bug?

As to Boot Camp and Windows... do I assume that this same GPU setup WOULD be supported if I run Blender that way?
Would Linux on the Mac be an option, too?

While inconvenient to reboot the machine between uses of Blender and my other software, if it allows me to stay up with the game while still using the power of my Mac's processors and memory it would be a useful interim measure. It seems that the only complete long term solution is to switch to a PC/Windows setup. In my case that comes with a heavy cost in terms of replacing my Mac software though.

...Chris

So despite CUDA not being available for my GPU in 2.9 it SHOULD still run on my Mac? The crash I get with Cycles and a mesh in a document is a bug? As to Boot Camp and Windows... do I assume that this same GPU setup WOULD be supported if I run Blender that way? Would Linux on the Mac be an option, too? While inconvenient to reboot the machine between uses of Blender and my other software, if it allows me to stay up with the game while still using the power of my Mac's processors and memory it would be a useful interim measure. It seems that the only complete long term solution is to switch to a PC/Windows setup. In my case that comes with a heavy cost in terms of replacing my Mac software though. ...Chris

So despite CUDA not being available for my GPU in 2.9 it SHOULD still run on my Mac? The crash I get with Cycles and a mesh in a document is a bug?

Yes, Blender should still run on macOS 10.13 and your hardware. The crash you're having will be investigated and hopefully fixed.

As to Boot Camp and Windows... do I assume that this same GPU setup WOULD be supported if I run Blender that way?

The NVIDIA GeForce GTX 980 Ti is supported for GPU rendering on Windows and Linux. Disclaimer: I currently don't have access to Apple hardware, therefore I can't tell with certainty if the GPU works well on Windows when using Boot Camp (especially if it's an eGPU?). There may still be some pitfalls with driver support that I'm not aware of.

Would Linux on the Mac be an option, too?

Theoretically, yes. I haven't done this myself though and based on a cursory search this may require more tinkering than dual booting Windows. IMHO I would only recommend this for developers and people with tech experience.

It seems that the only complete long term solution is to switch to a PC/Windows setup.

When Blender gets Vulkan support in the future and thereby support for Apple's Metal API through MoltenVK (or even a native implementation for the Metal API), then it would be possible to have feature parity on macOS again.

> So despite CUDA not being available for my GPU in 2.9 it SHOULD still run on my Mac? The crash I get with Cycles and a mesh in a document is a bug? Yes, Blender should still run on macOS 10.13 and your hardware. The crash you're having will be investigated and hopefully fixed. > As to Boot Camp and Windows... do I assume that this same GPU setup WOULD be supported if I run Blender that way? The NVIDIA GeForce GTX 980 Ti is supported for GPU rendering on Windows and Linux. Disclaimer: I currently don't have access to Apple hardware, therefore I can't tell with certainty if the GPU works well on Windows when using Boot Camp (especially if it's an eGPU?). There may still be some pitfalls with driver support that I'm not aware of. > Would Linux on the Mac be an option, too? Theoretically, yes. I haven't done this myself though and based on a cursory search this may require more tinkering than dual booting Windows. IMHO I would only recommend this for developers and people with tech experience. > It seems that the only complete long term solution is to switch to a PC/Windows setup. When Blender gets Vulkan support in the future and thereby support for Apple's Metal API through MoltenVK (or even a native implementation for the Metal API), then it would be possible to have feature parity on macOS again.
Member

I updated the docs in rBM6885.

I updated the docs in rBM6885.

Added subscriber: @Stefan_Werner

Added subscriber: @Stefan_Werner

@brecht @Stefan_Werner It seems that there are several people with similar issues on macOS:

I haven't merged them yet, because I can't verify if they have the same underlying cause (I don't have access to Apple hardware).

@brecht @Stefan_Werner It seems that there are several people with similar issues on macOS: - #79707 - #80469 - #80445 - #80315 I haven't merged them yet, because I can't verify if they have the same underlying cause (I don't have access to Apple hardware).
Member

At first glance, looks like those are older Mac Pros crashing on illegal instructions inside Embree. Possibly Embree is detecting the CPU capabilities incorrectly? I don't have access to a Mac of that generation though. Maybe we need to run our own CPU detection and tell Embree explicitly what to use.

At first glance, looks like those are older Mac Pros crashing on illegal instructions inside Embree. Possibly Embree is detecting the CPU capabilities incorrectly? I don't have access to a Mac of that generation though. Maybe we need to run our own CPU detection and tell Embree explicitly what to use.

Added subscribers: @Funtomas78, @iss

Added subscribers: @Funtomas78, @iss
Member

Added subscriber: @ankitm

Added subscriber: @ankitm

Added subscribers: @JoshPule, @3d4d5d6d7d8d

Added subscribers: @JoshPule, @3d4d5d6d7d8d

Added subscriber: @pier1971

Added subscriber: @pier1971

Added subscriber: @GiovanniBianchessi

Added subscriber: @GiovanniBianchessi

Sorry I'm not sure how this whole debug/revision system works but if I read this correctly there is a revision as yet untested on suitable hardware?
If so, am I able to test it for you on my Mac?
...Chris

Sorry I'm not sure how this whole debug/revision system works but if I read this correctly there is a revision as yet untested on suitable hardware? If so, am I able to test it for you on my Mac? ...Chris

Just to add, I have installed Blender 2.90 to my iMac (2014) with the same OS High Sierra 10.13.6 and everything runs fine.
It looks like that it is something related to the Mac Pro 2009 and 2010 that is causing the crash
Pier

Just to add, I have installed Blender 2.90 to my iMac (2014) with the same OS High Sierra 10.13.6 and everything runs fine. It looks like that it is something related to the Mac Pro 2009 and 2010 that is causing the crash Pier

@chrishartley

In #78793#1015556, @chrishartley wrote:
Sorry I'm not sure how this whole debug/revision system works but if I read this correctly there is a revision as yet untested on suitable hardware?

Yes, there is a patch in development that is not yet approved and thus not included in Blender.

If so, am I able to test it for you on my Mac?
...Chris

If you know how to build Blender yourself and how to use git to apply the patch, then you can test this yourself. Otherwise, you'll just have to wait until other developers have tested it, the patch is possibly revised based on feedback and once it is approved it will be included in Blender.

@chrishartley > In #78793#1015556, @chrishartley wrote: > Sorry I'm not sure how this whole debug/revision system works but if I read this correctly there is a revision as yet untested on suitable hardware? Yes, there is a patch in development that is not yet approved and thus not included in Blender. > If so, am I able to test it for you on my Mac? > ...Chris If you know how to [build Blender yourself](https://wiki.blender.org/wiki/Building_Blender/Mac) and how to use git to apply the patch, then you can test this yourself. Otherwise, you'll just have to wait until other developers have tested it, the patch is possibly revised based on feedback and once it is approved it will be included in Blender.
Member

Added subscriber: @EAW

Added subscriber: @EAW
Member

@chrishartley in addition to building Blender, you would have to build the updated OIDN library to apply all of the patch I believe. Either that or build without OIDN. As it involves a library update, I would personally wait until it is merged, and then test it out.

@chrishartley in addition to building Blender, you would have to build the updated OIDN library to apply all of the patch I believe. Either that or build without OIDN. As it involves a library update, I would personally wait until it is merged, and then test it out.

OK, sounds like I should wait :-)
Just thought I might be able to help as this particular blend of hardware may not be too avaoilable for testing on.
...Chris

OK, sounds like I should wait :-) Just thought I might be able to help as this particular blend of hardware may not be too avaoilable for testing on. ...Chris

Here's a test build with a potential fix:
https://download.blender.org/ftp/brecht/builds/blender-macos-simd-fix0.dmg

Can anyone test if it helps? I don't have the right hardware to test this.

Here's a test build with a potential fix: https://download.blender.org/ftp/brecht/builds/blender-macos-simd-fix0.dmg Can anyone test if it helps? I don't have the right hardware to test this.

@brecht Van Lommel (brecht)
Iv just tried on mc pro 5.1 os Mojave 10.14.6 amd WX5100 and render viewport and render still crashes on CPU.

@brecht Van Lommel (brecht) Iv just tried on mc pro 5.1 os Mojave 10.14.6 amd WX5100 and render viewport and render still crashes on CPU.

My Blender still crash when set to render in Cycles
my system Mac 5.1
OS High Sierra 10.13.6

My Blender still crash when set to render in Cycles my system Mac 5.1 OS High Sierra 10.13.6

I'm afraid it is the same for me. Still crashes when I try to view or render in cycles.

MacPro 5,1 running OS 10.13.6 High Sierra on a SSD
2 x 6 core Intel Xeon processors running at 3.46GHz
96 Gb RAM
Nvidia GeForce GTX 980 Ti running three screens

...Chris

I'm afraid it is the same for me. Still crashes when I try to view or render in cycles. MacPro 5,1 running OS 10.13.6 High Sierra on a SSD 2 x 6 core Intel Xeon processors running at 3.46GHz 96 Gb RAM Nvidia GeForce GTX 980 Ti running three screens ...Chris

Official release tested on Macbook pro mid 2012 os catalina 10.15.5. Working!!!

Official release tested on Macbook pro mid 2012 os catalina 10.15.5. Working!!!

Just tried and still crashes as before.
Anyway, thank you for the dmg.

Blender_2020-09-15-211933_iMac-di-Giovanni.crash

Just tried and still crashes as before. Anyway, thank you for the dmg. [Blender_2020-09-15-211933_iMac-di-Giovanni.crash](https://archive.blender.org/developer/F8886130/Blender_2020-09-15-211933_iMac-di-Giovanni.crash)

This issue was referenced by c65e4f4e39

This issue was referenced by c65e4f4e3970b192ec4f6033bd8253ca07411628

This issue was referenced by 007e90e8c0

This issue was referenced by 007e90e8c0a9176e16e70861d87dc7f883cc78ba

Removed subscriber: @brecht

Removed subscriber: @brecht

This issue was referenced by 7b988188dc

This issue was referenced by 7b988188dc3f5ea05d90b8e16337147778f9f580

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

Changed status from 'Needs Triage' to: 'Resolved'
Brecht Van Lommel self-assigned this 2020-09-18 18:13:53 +02:00

I managed to reproduce this in a virtual machine and found an alternative fix. The 2.91 macOS build on https://builder.blender.org/download/ has the fix, please let me know if it doesn't work.

I managed to reproduce this in a virtual machine and found an alternative fix. The 2.91 macOS build on https://builder.blender.org/download/ has the fix, please let me know if it doesn't work.

In #78793#1018733, @brecht wrote:
I managed to reproduce this in a virtual machine and found an alternative fix. The 2.91 macOS build on https://builder.blender.org/download/ has the fix, please let me know if it doesn't work.

Yupp.. Testing on my 2010 Mac Pro and now I can render happily. Both in viewport and Final 😃. Thank you..

> In #78793#1018733, @brecht wrote: > I managed to reproduce this in a virtual machine and found an alternative fix. The 2.91 macOS build on https://builder.blender.org/download/ has the fix, please let me know if it doesn't work. Yupp.. Testing on my 2010 Mac Pro and now I can render happily. Both in viewport and Final 😃. Thank you..

Yes works on mine too.

Thank you! You guys are brilliant!

Pier

Yes works on mine too. Thank you! You guys are brilliant! Pier

Me tooo!! Works. You changed my plans for weekend. My girlfriend will not like it. Thank you very much guys.
Jan

Me tooo!! Works. You changed my plans for weekend. My girlfriend will not like it. Thank you very much guys. Jan

...and on mine!
Thanks for persevering, guys.
It is much appreciated
...Chris

...and on mine! Thanks for persevering, guys. It is much appreciated ...Chris

I let you know that it works.
Thank you!

Regards
Giovanni

I let you know that it works. Thank you! Regards Giovanni

Added subscriber: @GBRS

Added subscriber: @GBRS

Hi there. Ok I got a little lost in reading all the above. So am I right that as of today, no fix or workaround has been found to use an Nvidia GPU in Blender 2.90/1/2. even if we are in High Sierra on any mac build at all and in the end a workaround was found for the CPU crashes but the GPU couldn't be. And no one has access to a version where it's possible to use? A read a guy mention a 2020 June build of 2.9 that still worked, but I can't find that version online anywhere. Advice is so welcome, Gerard

Hi there. Ok I got a little lost in reading all the above. So am I right that as of today, no fix or workaround has been found to use an Nvidia GPU in Blender 2.90/1/2. even if we are in High Sierra on any mac build at all and in the end a workaround was found for the CPU crashes but the GPU couldn't be. And no one has access to a version where it's possible to use? A read a guy mention a 2020 June build of 2.9 that still worked, but I can't find that version online anywhere. Advice is so welcome, Gerard
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
14 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#78793
No description provided.