Hi, shaunsingh0207!
After your message, I downloaded both the 2.93.0 for Apple silicon and Intel x86. It turns out that it was something iffy with 2.92.0 that made EEVEE really slow. You are right; EEVEE did not see much change, while cycles did speed up, for me 40-50 percent. Thank you so much for your reply!

A basic run-through feels much snappier than before; thanks to all Blender contributors for taking it so far! 🙌

Hi! Firstly, EEVEE rendering is run on the GPU, while Cycles rendering is run on the CPU. Since EEVEE rendering is run on the gpu, the code was already largely native, which means EEVEE isn't going to see many performance improvements in the native build.

Hi! I’m pretty new to Blender, and even newer to the Blender community. I’ve only been using Blender for around a year or so. I have noticed a few nuances, just from the first few times of using it. Here are my specs:

MacBook Pro 13 M1 (1TB SSD, 16GB RAM)

First, I would like to thank everyone who has worked on this. The startup time for Blender is so much faster, and it is GREAT. Also, Eevee rendering is around 2.5 times faster for me (92-ish down to 38 seconds).

There is now a macOS arm64 build on:
https://builder.blender.org/download/

Probable duplicate of T83791: Blender crash on iMac Pro with Big Sur

So, for what it's worth, I changed this line: https://git.blender.org/gitweb/gitweb.cgi/blender.git/blob/HEAD:/intern/cycles/render/osl.cpp#l171

I've tested the latest M1 build from Stephan Werner and it does not exhibit this issue (great news for the future), so it suggests this issue is related to AMD mac drivers not playing well with Blender. My current workstation is a 2013 Mac Pro, which is a highly capable machine, along with many other macs with AMD graphics. I sincerely hope this longstanding bug can finally get fixed ASAP so we can start using Blender on our workstations again.

I have exactly the same problem.
I Select the Cube (or any mesh) in the viewport and Add a Particle System.
I Change to Hair Type and Blender crashes immediately.

I mistakenly left this on a similar thread that had been closed as a duplicate so wanted to repost it here. I've performed fresh installs of Blender multiple times and disabled all addons. I hope to try again when new Macs are available but unfortunately for now I will have to move back to Modo.

I cannot reproduce the problem. It must be something specific to macOS

Sharp is the distribution in the Glass shader. The file is set up to use Beckmann.
Your viewport seems correct though. Could be something specific to Iris Plus 655 though =\

This on an Apple MacBook Pro 13" from 2016 with an Intel 540, not sure what you mean with Sharp though:

I can confirm this happens on my 2013 mac pro with D700 graphics.

Adding macOS tag if issue is related to mac devices .

Had to move to a 2019 iMac running 10.14.6 (18G8022) temporarily and hair works fine. Still crashing on leave and return though. 2.92.0 2021-02-25

This has rendered Blender almost unusable for me. If I leave Blender for a few minutes it will crash when I begin working again. The only way I can preserve a rendering is to have it written to disk before touching Blender again which reduces the effectiveness of the compositor substantially. This is on a 2019 iMac running 10.14.6 (18G8022). This is consistent with my experience on a 2013 Mac Pro running Catalina.
Model Identifier: iMac19,2

Processor Name:	Intel Core i5
Processor Speed:	3 GHz
Number of Processors:	1
Total Number of Cores:	6
L2 Cache (per Core):	256 KB
L3 Cache:	9 MB
Memory:	32 GB
Boot ROM Version:	1554.80.3.0.0
SMC Version (system):	2.47f2

Working fine on an older MacBook Pro 13" with just an Intel HD 4000, running on macOS 10.15.7, as mentioned in https://developer.blender.org/T75832

@Nate (nlate) I just tried Blender 2.93 Alpha 321eef6a0c0f from April 3rd 2021 on an older MacBook Pro 13" with Intel HD 4000 running macOS 10.15.7 and there I can not reproduce the crash, this without a "Load Factory Settings" though...

Blender 2.93 Alpha is still crashing when adding hair to default cube on Macs.

I am also having this issue, but it seems to be Mac only. Default cube, add particle system, change to hair, crash. Every time.

In T86025#1138816, @Pete Thorne (ee0pdt) wrote:

To the devs in the Blender team watching this: What should the affecting Mac community do? Seems there is a potential for a new option to invert orbit, should this bug report be changed to a feature request? Or should we make a new request somewhere?

In the meantime, we're all a bit frustrated and just want to get on with building stuff without having to relearn what was natural to us up to now.

To the devs in the Blender team watching this: What should the affecting Mac community do? Seems there is a potential for a new option to invert orbit, should this bug report be changed to a feature request? Or should we make a new request somewhere?

I don't think this is still an issue. Tested with recent build of version 2.93.0 alpha . Could you test that again??

Since this is reported so often, will dare setting to High priority.

Actually, we have a duplicate report for this, see T83199: Blender crashes when adding a particle system to a mesh object and switching the type to Hair, so will merge these reports.

I am having the same problem and, was able to recreate the problem as mentioned above.

I have also encountered this issue, also on macos

Probable duplicate of T83791: Blender crash on iMac Pro with Big Sur

No crash on darwin 18, Intel HD Graphics 6000
Both 2.92 and rB2600b27d2647acfc9ddc19084b10db673b46a95a master.

Hi Guys, have there been any solutions of workarounds so far? thanks!

@Ankit jain (Ankit)

That's bad advice. See the To: and CC section of your emails to see who's listening. Concern is not a replacement for bug report.

In T86025#1134260, @Ankit Meel (ankitm) wrote:

If this change has been as much of a headache for you as it has been for me, go over there and make some noise about about.

That's bad advice. See the To: and CC section of your emails to see who's listening. Concern is not a replacement for bug report.

---

@Julian Eisel (Severin) could you change the status of the report please ? @Yevgeny Makarov (jenkm) already expressed his take above.

If this change has been as much of a headache for you as it has been for me, go over there and make some noise about about.

That's bad advice. See the To: and CC section of your emails to see who's listening. Concern is not a replacement for bug report.

Hey everyone! There is currently better place to voice your opinions about this change. This thread is a bug report, but because it is not considered a bug by the developers, it will likely only get glossed over. If you want to have a better chance at getting a toggle, the feature commit is the best place to do it!