Bug Frequent crashes on Apple M1 Max w Unity 2022.2.5f1

I've been experiencing frequent crashes both in Editor and in packaged MacOS Builds. This has been happening for a while now (back to 2022.2.1f1 possibly), and is a major disruption to our workflow. This needs to be fixed asap.

This is on latest URP renderer.

It appears to be related to Particle FX according this native crash stack collected from a Development build:

```
Exception Type: EXC_CRASH (SIGSEGV)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: VoidStriker [11213]

Thread 0:: tid_103 Dispatch queue: com.apple.main-thread
0 UnityPlayer.dylib 0x1101684c8 Mesh::GetSubMeshBuffer16(int) + 16
1 UnityPlayer.dylib 0x10fc76d7c ParticleSystemRenderer::UpdateCachedMesh() + 584
2 UnityPlayer.dylib 0x10fc76af4 ParticleSystemRenderer::AwakeFromLoad(AwakeFromLoadMode) + 56
3 UnityPlayer.dylib 0x10f828d14 AwakeFromLoadQueue::InvokeAwakeFromLoad(AwakeFromLoadQueue::Item*, unsigned int, AwakeFromLoadMode) + 172
4 UnityPlayer.dylib 0x10f828ba0 AwakeFromLoadQueue::AwakeFromLoadAllQueues(AwakeFromLoadMode, bool) + 72
5 UnityPlayer.dylib 0x10f0143e0 AwakeAndActivateClonedObjects(Object**, vector_map<int, int, std::__1::less<int>, stl_allocator<std::__1:air<int, int>, (MemLabelIdentifier)1, 16> > const&) + 820
6 UnityPlayer.dylib 0x10f0154a8 InstantiateObject(Object&, Vector3f const&, Quaternionf const&) + 112
7 UnityPlayer.dylib 0x10eb2f180 Object_CUSTOM_Internal_InstantiateSingle_Injected(ScriptingBackendNativeObjectPtrOpaque*, Vector3f const&, Quaternionf const&) + 212
8 ??? 0x1673ad5dc ???
9 ??? 0x1673ad500 ???
10 ??? 0x1673ad324 ???
11 ??? 0x1673ad1d8 ???
12 ??? 0x1673af3b4 ???
13 ??? 0x1673af17c ???
14 ??? 0x1673ae8a4 ???
15 ??? 0x1673ae424 ???
16 ??? 0x1673ae05c ???
17 ??? 0x162c8739c ???
18 libmonobdwgc-2.0.dylib 0x119ef08c8 0x119ee0000 + 67784
19 libmonobdwgc-2.0.dylib 0x11a07744c 0x119ee0000 + 1668172
20 libmonobdwgc-2.0.dylib 0x11a07736c mono_runtime_invoke + 100
21 UnityPlayer.dylib 0x10f7baf7c scripting_method_invoke(ScriptingMethodPtr, ScriptingObjectPtr, ScriptingArguments&, ScriptingExceptionPtr*, bool) + 72
22 UnityPlayer.dylib 0x10f7a2e04 ScriptingInvocation::Invoke(ScriptingExceptionPtr*, bool) + 164
23 UnityPlayer.dylib 0x10f7925c4 MonoBehaviour::HandleNotifications(void*, int, MessageData&) + 456
24 UnityPlayer.dylib 0x10edd94e8 GameObject::SendMessageAny(MessageIdentifier const&, MessageData&) + 476
25 UnityPlayer.dylib 0x10f6c0fdc PhysicsManager::SendOnCollisionEnter(Unity::Component*, ScriptingObjectPtr) + 88
26 UnityPlayer.dylib 0x10eb984e4 Physics_CUSTOM_SendOnCollisionEnter(ScriptingBackendNativeObjectPtrOpaque*, ScriptingBackendNativeObjectPtrOpaque*) + 276
27 ??? 0x1673aa4fc ???
28 ??? 0x1673a915c ???
29 ??? 0x1673a8b20 ???
30 ??? 0x1673a8db8 ???
31 libmonobdwgc-2.0.dylib 0x119ef08c8 0x119ee0000 + 67784
32 libmonobdwgc-2.0.dylib 0x11a07744c 0x119ee0000 + 1668172
33 libmonobdwgc-2.0.dylib 0x11a07736c mono_runtime_invoke + 100
34 UnityPlayer.dylib 0x10f7baf7c scripting_method_invoke(ScriptingMethodPtr, ScriptingObjectPtr, ScriptingArguments&, ScriptingExceptionPtr*, bool) + 72
35 UnityPlayer.dylib 0x10f7a2e04 ScriptingInvocation::Invoke(ScriptingExceptionPtr*, bool) + 164
36 UnityPlayer.dylib 0x10f974454 PhysicsScene:rocessContacts() + 120
37 UnityPlayer.dylib 0x10f973cdc PhysicsScene:rocessReports() + 76
38 UnityPlayer.dylib 0x10f6bdb8c PhysicsManager::Simulate(int, float) + 3408
39 UnityPlayer.dylib 0x10f6bbcbc PhysicsManager::InitializeClass()::FixedUpdatePhysicsFixedUpdateRegistrator::Forward() + 128
40 UnityPlayer.dylib 0x10f2f0ea4 ExecutePlayerLoop(NativePlayerLoopSystem*) + 188
41 UnityPlayer.dylib 0x10f2f0ee4 ExecutePlayerLoop(NativePlayerLoopSystem*) + 252
42 UnityPlayer.dylib 0x10f2f1200 PlayerLoop() + 324
```

 

While the above call stack happens the most often. This URP Gfx Shadow related crash also occurs regularly, within builds and in editor:

```
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [12125]

VM Region Info: 0 is not in any region. Bytes before following region: 4363714560
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 104190000-104194000 [ 16K] r-x/r-x SM=COW ...S/VoidStriker

Thread 0 Crashed:: tid_103 Dispatch queue: com.apple.main-thread
0 UnityPlayer.dylib 0x10eaa59b4 ScriptableRenderLoopShadowsJob(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*) + 72
1 UnityPlayer.dylib 0x10efc5f08 GfxDevice::ExecuteAsync(int, void (*)(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*), GfxDeviceAsyncCommand::ArgScratch**, GfxDeviceAsyncCommand::Arg const*, JobFence const&) + 80
2 UnityPlayer.dylib 0x10efc5f08 GfxDevice::ExecuteAsync(int, void (*)(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*), GfxDeviceAsyncCommand::ArgScratch**, GfxDeviceAsyncCommand::Arg const*, JobFence const&) + 80
3 UnityPlayer.dylib 0x10ea9d6f4 ScheduleRenderJobs(unsigned int, ScriptableRenderLoopShadowsArg const*, JobFence const&) + 748
4 UnityPlayer.dylib 0x10ea9d314 ExecuteDrawShadowsCommand(SlicedDrawShadow const&) + 872
5 UnityPlayer.dylib 0x10eaa24f8 ScriptableRenderContext::ExecuteScriptableRenderLoop() + 1416
6 ??? 0x28e7f6afc ???
7 ??? 0x28e7f6a34 ???
8 ??? 0x28e7f69c4 ???
9 ??? 0x28e76ed18 ???
10 ??? 0x28e7588dc ???
11 ??? 0x28e752ae0 ???
12 ??? 0x28e7522e4 ???
13 ??? 0x28e6e4b94 ???
14 ??? 0x28e6e4ee4 ???
15 libmonobdwgc-2.0.dylib 0x114f0c8c8 0x114efc000 + 67784
16 libmonobdwgc-2.0.dylib 0x11509344c 0x114efc000 + 1668172
17 libmonobdwgc-2.0.dylib 0x11509336c mono_runtime_invoke + 100
18 UnityPlayer.dylib 0x10f072f7c scripting_method_invoke(ScriptingMethodPtr, ScriptingObjectPtr, ScriptingArguments&, ScriptingExceptionPtr*, bool) + 72
19 UnityPlayer.dylib 0x10f05ae04 ScriptingInvocation::Invoke(ScriptingExceptionPtr*, bool) + 164
20 UnityPlayer.dylib 0x10eaa3dc4 ScriptableRenderContext::ExtractAndExecuteRenderPipeline(dynamic_array<Camera*, 0ul> const&, void (*)(SceneNode const*, AABB const*, IndexList&, SceneCullingParameters const*), void*, ScriptingObjectPtr) + 392
21 UnityPlayer.dylib 0x10e73b718 RenderManager::RenderCamerasWithScriptableRenderLoop(int) + 800
22 UnityPlayer.dylib 0x10e73be3c RenderManager::RenderCameras(int, void (*)(), void (*)()) + 64
23 UnityPlayer.dylib 0x10ebb5e2c PlayerRender(bool) + 996
24 UnityPlayer.dylib 0x10ebb6f50 InitPlayerLoopCallbacks():ostLateUpdateFinishFrameRenderingRegistrator::Forward() + 80
25 UnityPlayer.dylib 0x10eba8ea4 ExecutePlayerLoop(NativePlayerLoopSystem*) + 188
26 UnityPlayer.dylib 0x10eba8ee4 ExecutePlayerLoop(NativePlayerLoopSystem*) + 252
27 UnityPlayer.dylib 0x10eba9200 PlayerLoop() + 324
```

 

I don't have any helpful comments, but I just wanted to share that I am also experiencing the same

ScriptableRenderLoopShadowsJob

crash on a regular basis.

My machine:

2021 Macbook Pro
Apple M1 Max
macOS 12.2.1
-- running Unity 2022.2.4f1

 

It might be a coincidence, but it feels like 2022.2.6f1 has been a bit more stable compared to the versions before it.

 

Will update to 2022.2.6f1 and give it a try. Thanks for the heads up @Hendrik-Mans

 

Correction, it was actually Unity 2022.2.4f1 that I was running when logging these crashes above. I since tried to test out 2022.2.6f1, but that version (and actually starting 2022.2.5f1) has corrupted my shader files. So need to figure out what's going on with that. Thanks Unity!

 

2022.2.5 and 2022.2.6 are both crashing for me too. Tried to change the Quality to Balanced. So far didn't crash. Maybe will also work for someone.

 

I'm also consistently having render pipeline crashes using Unity 2022.2.6f1, on my Mac Pro M1.
I'm attaching my Crash logs.

 

I'm using Unity 2022.2.6f1 and getting the same crashes on many android devices

 

Same crash (second one) as me @vectorized-runner in ScriptableRenderLoopShadowsJob. Everyone try to post your crash stacks, so Unity can see it is a common issue, and hopefully fix this in 2022.2.7f1

 

Crashing like crazy on my Intel Mac Pro running 2022.2.5f1. Crashes so randomly. If I save a scene, Crash.

 

Anyone from Unity Technologies here? I mean this is a serious issue, we are before EA release of our game https://store.steampowered.com/app/1961600/Darfall/ and the silicon mac m1 versions keep crashing even in player build with the 2022.2+ versions, it was not happening with previous 2022.1 versions. So there is some breaking change between 2022.1 and 2022.2

I tried all versions from 2022.2.1 up to 2022.2.6 and they all crash the same.

mono_crash.json files: https://easyupload.io/m/dnr2on

 

Experiencing the same issue frequently; easiest to reproduce the `ScriptableRenderLoopShadowsJob` crash with the frame debugger in play mode.

Model Name: MacBook Pro
Model Identifier: MacBookPro18,4
Chip: Apple M1 Max
Running Monterey
Unity 2022.2.6f1

 

This is crashing me several times per day in Play Mode in 2022.2.4f1. I'm using the HDRP. It's been happening for a few weeks now.

I'll see if anything changes after grabbing the latest release.

 

Nope latest 2022.2.7f1 still has these issues.

 

@Phil_Z it appears you work at Unity. Could you escalate these issues internally please?

 

This only seems to happen in new versions of Unity, when I downgraded to 2021.3.17 all these errors were gone

 

@Tautvydas-Zilys these are 2 High Pain crashes as well. Rendering packaged builds unusable. I filed a bug report last week, hoping we could vote it up lol, but unfortunately the triage closed the issue as a duplicate of some other unrelated call stack. Would you mind marking these High Pain as well? Thanks!

 

@Tautvydas-Zilys here's the issue I filed:
https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-25831

 

Oops my bad. I linked the duplicate linked in the response to closing my bug report, which was actually CASE IN-31437.
Perhaps they are the same (both Gfx related), but the call stack looks a bit different, and the repro steps. I added comments to that remaining issue.

 

Thanks @Tautvydas-Zilys!

I updated to the latest 2022.2.8f1 and these crashes are still an issue. I see that the duplicate issue linked above is now mentioned as Known Issue in the release notes. We really need this fixed in the next update. Adding any VFX at all in particular causes this Shadow Job crash to happen more frequently (within 20 secs of play for me). So right now I have had to disable all my VFX to get any work done.

 

@Tautvydas-Zilys we're experiencing those crashes as well on M1 (very often).

 

As nobody mentioned it in this thread. Start your editor with the command line argument (click 3 dots in unity hub, next to your project): -force-gfx-st

I had the editor crash every 5-10 minutes on my M1 Pro, this fixed it for me. Of course this is a workaround and not a permanent fix

 

Thanks for the tip @Ripple196!
I was not aware of the 3 dots cmd line access functionality.

 

Note that this option disables Frame Debugger.

 

Hi, If it helps the Unity staff in this thread, I'm seeing this crash too, on Android. Here's the details:

Galaxy Tab S7 FE
SM-T733
It's running Android 13

Unity 2022.2.7f1


#00 0x0000000000bde948 Mesh::GetSubMeshBuffer16(int)
#01 0x0000000000b07008 ParticleSystemRenderer::UpdateCachedMesh()
#02 0x0000000000b06d94 ParticleSystemRenderer::AwakeFromLoad(AwakeFromLoadMode)
#03 0x0000000000601ae8 AwakeFromLoadQueue::InvokeAwakeFromLoad(AwakeFromLoadQueue::Item*, unsigned int, AwakeFromLoadMode)
#04 0x00000000006019c4 AwakeFromLoadQueue::AwakeFromLoadAllQueues(AwakeFromLoadMode, bool)
#05 0x00000000004209cc AwakeAndActivateClonedObjects(Object**, vector_map<int, int, std::__ndk1::less<int>, stl_allocator<std::__ndk1:air<int, int>, (MemLabelIdentifier)1, 16> > const&)
#06 0x0000000000421384 InstantiateObject(Object&, Vector3f const&, Quaternionf const&)
#07 0x000000000039f230 Object_CUSTOM_Internal_InstantiateSingle_Injected(ScriptingBackendNativeObjectPtrOpaque*, Vector3f const&, Quaternionf const&)
#08 0x0000000002022d1c Object_Internal_InstantiateSingle_Injected_m3DD1967FF5D58E4B4D8242A926DFD5C1AD0872CD
#09 0x0000000002022ba0 Object_Instantiate_m99C9917ED3F7B2B9C569B55F52411620B52DA19D
...

 

The new patch 2022.2.9 seems to haved fixed the scriptablerenderloop crashes for me. I removed the -force-gfx-st and did not have a single crash today.

The Release notes suggest that the issue was solved and so far I can confirm

 

No it's not fixed, its still in the known issues page. Just upgraded and still crashing.

 

Same thing across 2022.* and 2023.*

 

This is an extremely fatal error for MacOS developers. I am having problem with version 2022.2.6f1 A level where project development is impossible at all. Looks like I'll have to ditch my MacBook and switch to a Windows laptop.

Whatever project you are trying to do with URP, it will crash sooner or later.

Obtained 77 stack frames.

#0 0x00000102b25784 in ScriptableRenderLoopShadowsJob(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*)

#1 0x00000102e83040 in GfxDevice::ExecuteAsync(int, void (*)(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*), GfxDeviceAsyncCommand::ArgScratch**, GfxDeviceAsyncCommand::Arg const*, JobFence const&)

 

@jasonkang_unity have you tried adding this to your cmd line (via Unity Hub)? It reduced the frequency of crashes for me, but does not eliminate entirely.

-force-gfx-st

 

@Tautvydas-Zilys any update on getting this fix into a release soon?
This is a real bad look for Unity. All other work should be put on hold until this is fixed.

You should love your MacOS users, cause Windows users are switching to UE5. lol

 

Thank you for the information. It's not perfect, but the frequency of crashes has decreased to some extent.

 

The worst thing is that macOs builds are crashing as frequently as Editor. And launching arguments is not helping in builds.

 

2022.2.11f1 crashes after every couple of minutes of work

 

Every silicon version I tried is crashing almost constantly with maximum uninterrupted sessions lasting about 20-30mins. This is incredibly frustrating and I have no idea what to do.

 

I can confirm that this made crashes far less frequent for me as well. Thanks a lot for the tip.

 

Thanks for the update @Tautvydas-Zilys

 

Same for me. Adding the argument doesn't solve much.
Most of the time session duration is about 1minute.

 

@Tautvydas-Zilys what's the timeline on this fix? I just updated to 2022.2.13f1 and this issue seems worse now, with -force-gfx-st not providing a work around anymore. This is a serious problem for many, so I hope Unity includes a fix in the very next release.

 

Confirming what others have said, it's even worse on last versions 2022.2.11, 12 and 13. Unity 2023 beta as well.
probably some common change they made on both versions recently I guess, it makes it impossible to work on a Mac since it crashes in less then 3-5 minutes.

 

Still happening for me in 2022.2.14f1, 2023 M2 Macbook Pro.
Related post here - https://forum.unity.com/threads/frequent-crashes-on-m1-with-2022-2-does-unity-care.1401649/

 

@Tautvydas-Zilys it looks like this issue is still not fixed in 2022.2.14f1, yet Unity has removed it from the known issues list. I am worried that this implies a lack of priority to fix this terrible issue for MacOS users. Here we are almost 10 releases later and still nothing.

Why is this not called out in Known Issues anymore?
https://unity.com/releases/editor/whats-new/2022.2.14

• RP Foundation: [Silicon] Crash on ScriptableRenderLoopJob when machine is left idle while the Editor is in Play mode (UUM-25831)

 

Cool! I figured that was the case, since the issue tracker said that a fix was in review.

 

I can confirm, it was not fixed. Had a lot of crashes due to this issue during the last two days.