Sometimes while playing it also gets stuck at Updating Geometry BVH Mball and most of the UI gets unresponsive.

In general, playing animations in cycles rendered view has a very high tendency to crash, they seems to occur much more often than on my previous intel Mac..

@Germano Cavalcante (mano-wii) Can you check?

Still happens with 3.0 final release.

Hi, thanks for testing. With factory defaults I can still easily reproduce this in 3.0 final release and in the latest 3.1 daily build (version: 3.1.0 Alpha, branch: master, commit date: 2021-12-07 16:47, hash: rBa37dac0a884f). The crashes basically happen while doing anything in cycles rendered view, but occur most often and consistently when playing animations in the viewport. Sometimes within seconds of pressing play, sometimes after up to a few minutes; when just editing I will run into a crash within 15-30 minutes usually. It is about 50/50 whether blender fully crashes or only the ui locks up without a crash.

The crashes are specific to the apple silicon build, when I use the intel version on the same m1 MacBook Pro, the crashes do not occur. Unfortunately I can't give more specific steps than above to reproduce, I can add more crash reports if that is helpful.

Sometimes I also get this effect where the rendered view stops updating, a few clicks after that the ui will completely lock up:

Same with metal GPU enabled, frequent crashes in rendered viewport. One report with metal enabled just in case the problem might be different:

I can reproduce the crash as well as viewport shading not updating using the boat boating blend file. For me, Blender crashes after 10 to 60s when using CPU rendering. I just go into viewport shading and start the animation, then leave Blender alone.

I could not reproduce with GPU rendering (within a reasonable amount of time).

System Information
Operating system: macOS-12.1-arm64-arm-64bit 64 Bits
Graphics card: Apple M1 Pro Apple 4.1 Metal - 76.3

Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-07 23:28, hash: rB741ed5fcd2e2

@Michael (michael64) can you see if this is the same as T94736? I get a lot of crashes in rendered view with the M1 build (but not in the intel one); it is hard to see if it is all the same bug(s) or if I need to file multiple reports.

@Wouter Stomp (wouterstomp), this crash is very different from T94736.
As one can see in F11826548 thread 16 calls ccl::BVHEmbree::build which calls embree::sse2::BVHBuilderMorton::BuildPrim via tbb which crashes in thread 17.
The Cycles Metal implementation is not involved here at all.
I suspect this is the case even for the F12737533 but there macOS could not even create a proper crash report so I can't say for sure.

I tried to reproduce the crash on Apple M1 and got three crashes so far but always by doing random UI interactions and I found no way of forcing a crash or even make it more likely.
So multiple bugreports are definitely called for here.
Also if you like you could upgrade to macOS 12.1. This will not make the crash go away but it might help in generating a proper crash report when using Metal.

Yes, both crashes and the UI freezing still occur with the latest 3.1 build
I get these crashes a lot (like every few minutes) whenever doing anything in cycles rendered view, not only with this file.

Crash log reproduced with the same .blend:

System Information
Operating system: macOS-12.2-arm64-arm-64bit 64 Bits
Graphics card: Apple M1 Max Apple 4.1 Metal - 76.3

Blender Version
Broken: version: 3.1.0 Beta, branch: master, commit date: 2022-02-09 17:06, hash: rBd1202bd641ca

Latest 3.2 dailies are also affected. One thing I noticed just now (as Leonard reported above) is that the crashes occur much faster/often when using the CPU than when using the GPU.