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::pair<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::processContacts() + 120
37 UnityPlayer.dylib 0x10f973cdc PhysicsScene::processReports() + 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
1 Like
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()::postLateUpdateFinishFrameRenderingRegistrator::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 sameScriptableRenderLoopShadowsJob crash on a regular basis.
My machine:
2021 Macbook Pro
1 Like
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!
AliBuck
February 14, 2023, 11:13pm
7
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.
8807380–1197898–crash.txt (13.6 KB)
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
1 Like
Crashing like crazy on my Intel Mac Pro running 2022.2.5f1. Crashes so randomly. If I save a scene, Crash.
Wrymnn
February 17, 2023, 6:34pm
12
Anyone from Unity Technologies here? I mean this is a serious issue, we are before EA release of our game Darfall on Steam 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: Upload Files | Free File Upload and Transfer Up To 20 GB
Experiencing the same issue frequently; easiest to reproduce the ScriptableRenderLoopShadowsJob crash with the frame debugger in play mode.
Model Name: MacBook Pro
1 Like
allworknoplay:
Experiencing the same issue frequently; easiest to reproduce the ScriptableRenderLoopShadowsJob crash with the frame debugger in play mode.
Model Name: MacBook Pro
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
1 Like
@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!
jazzay22:
@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!
If you can give me a bug number, I can look at what happened with the bug.
@Tautvydas-Zilys here’s the issue I filed: