Unity Issue Tracker - [Silicon] Crash on ScriptableRenderLoopJob when machine is left idle while the Editor is in Play mode

Fixed

Fixed in 2022.2.17f1, 2023.1.0b14, 2023.2.0a11

Votes

129

Found in

2022.2.5f1

2023.1.0b2

2023.2.0a6

Issue ID

UUM-25831

Regression

No

[Silicon] Crash on ScriptableRenderLoopJob when machine is left idle while the Editor is in Play mode

Jan 30, 2023

Reproduction steps:
1. Open the attached project “URPrepro”
2. Open the “StarSystem” Scene
3. Enter the Play mode
4. Leave the machine idle

Expected result: Editor stays in the Play mode
Actual result: Editor crashes after some time of leaving it idle

Reproducible with: 14.0.6 (2022.2.5f1), 15.0.4 (2023.1.0b2)
Couldn’t test with: 10.10.1 (2020.3.44f1) - No Silicon Editor, 12.1.10 (2021.3.18f1) Console error - “Assets/UI Toolkit/Scripts/RadialProgress.cs(59,9): error CS0246: The type or namespace name 'Painter2D' could not be found (are you missing a using directive or an assembly reference?)”

Reproducible on: MacOS 13.1 (M1 Max)
Not reproducible on: MacOS 13.1 (Intel), Windows 10

Notes:
Doesn’t reproduce with Rosetta.
Other users have reported URP crashes with the same stack trace but different steps.

First lines of the stack trace:
#0 0x000001048e7104 in ScriptableRenderLoopJob(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*)
#1 0x00000104c2b1d8 in GfxDevice::ExecuteAsync(int, void (*)(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*), GfxDeviceAsyncCommand::ArgScratch*{*}, GfxDeviceAsyncCommand::Arg const{*}, JobFence const&)
#2 0x000001048e3e6c in ScheduleRenderJobs(unsigned int, ScriptableRenderContextArg const*, JobFence const&)
#3 0x000001048e39c4 in ExecuteDrawRenderersCommand(ScriptableRenderContextArg*)
#4 0x000001048d7628 in ScriptableRenderContext::ExecuteScriptableRenderLoop()
#5 0x0000032da8afec in (wrapper managed-to-native) UnityEngine.Rendering.ScriptableRenderContext:Submit_Internal_Injected (UnityEngine.Rendering.ScriptableRenderContext&) [

{0x14fa71738}

+ 0x6c] (0x32da8af80 0x32da8b04c) [0x12cf42a80 - Unity Child Domain]

Resolution Note (fix version 2023.2.0a11):

Crash fixed in ScriptableRenderLoop that occured on Silicon/IOS/Android resolved. This possibly solves other crashes related to the job system on these platforms.
Resolution Note (fix version 2023.1.0b14):

Fixed common crash on IOS/Android/Silicon platforms. Most commonly crashed in ScriptableRenderLoop.

Comments (47)

alexanderameye

Mar 25, 2023 17:43

Same issue! Really annoying
Loran75

Mar 25, 2023 10:04

Has anyone found a workaround to avoid this bug until Unity finally fixes it?
circuscompany

Mar 24, 2023 07:25

I too have the same problem on android.

Tested on Unity 2022.2.9 and 2022.2.11.

/lib/arm64/libunity.so (ScriptableRenderLoopJob(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*))
/lib/arm64/libunity.so (GfxDevice::ExecuteAsync(int, void (*)(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*), GfxDeviceAsyncCommand::ArgScratch**, GfxDeviceAsyncCommand::Arg const*, JobFence const&))
/lib/arm64/libunity.so (ScheduleRenderJobs(unsigned int, ScriptableRenderContextArg const*, JobFence const&))
/lib/arm64/libunity.so (ExecuteDrawRenderersCommand(ScriptableRenderContextArg*))
/lib/arm64/libunity.so (ScriptableRenderContext::ExecuteScriptableRenderLoop())
/lib/arm64/libil2cpp.so (UniversalRenderPipeline_RenderSingleCamera_mAED46E947EC1009B5D51EE35B156C551A2901A18)
/lib/arm64/libil2cpp.so (UniversalRenderPipeline_RenderCameraStack_m47BBC0B4111D83BB6EE3275C9572BFBF2F5451B9)
/lib/arm64/libil2cpp.so (UniversalRenderPipeline_Render_m15A42AB44C14AB4DCA7EF0B915964D46B643D50E)
/lib/arm64/libil2cpp.so (RenderPipelineManager_DoRenderLoop_Internal_mB646C8738F4A9859101F3BE94809E2E10BBDB1FB)
/lib/arm64/libil2cpp.so (il2cpp::vm::Runtime::InvokeWithThrow(MethodInfo const*, void*, void**))
/lib/arm64/libil2cpp.so (il2cpp::vm::Runtime::Invoke(MethodInfo const*, void*, void**, Il2CppException**))
/lib/arm64/libunity.so (scripting_method_invoke(ScriptingMethodPtr, ScriptingObjectPtr, ScriptingArguments&, ScriptingExceptionPtr*, bool))
/lib/arm64/libunity.so (ScriptingInvocation::Invoke(ScriptingExceptionPtr*, bool))
/lib/arm64/libunity.so (ScriptableRenderContext::ExtractAndExecuteRenderPipeline(dynamic_array<Camera*, 0ul> const&, void (*)(SceneNode const*, AABB const*, IndexList&, SceneCullingParameters const*), void*, ScriptingObjectPtr))
/lib/arm64/libunity.so (RenderManager::RenderCamerasWithScriptableRenderLoop(int))
/lib/arm64/libunity.so (RenderManager::RenderCameras(int, void (*)(), void (*)()))
/lib/arm64/libunity.so (PlayerRender(bool))
/lib/arm64/libunity.so (ExecutePlayerLoop(NativePlayerLoopSystem*))
/lib/arm64/libunity.so (ExecutePlayerLoop(NativePlayerLoopSystem*))
/lib/arm64/libunity.so (PlayerLoop())
/lib/arm64/libunity.so (UnityPlayerLoop())
/lib/arm64/libunity.so (nativeRender(_JNIEnv*, _jobject*))
/oat/arm64/base.odex (art_jni_trampoline+116)
jasonkang_unity

Mar 24, 2023 04:28

This is an extremely fatal error for MacOS developers. I am having problem with version 2022.2.6f1(on M1 Pro) 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&)
georgesdimitrov

Mar 24, 2023 04:14

I'm also getting this within 30 seconds of hitting play, it's really really annoying. I don't understand how such a critical issue is not being fixed. I tested it with 2022.2.11, 12 and even 2023.1.0b8 just in case.
tebrackin

Mar 20, 2023 03:36

I am having this issue with 2021-2023 versions on a brand new M2Pro. Can't even load a new project without it crashing the whole computer.
Loran75

Mar 18, 2023 21:13

Many releases later, this huge problem is still here...
Generally speaking, when you see the number of crashes and freezes with most versions (including LTS), I think Unity doesn't care about macOS, iOS developers :)
timgreenberg

Mar 17, 2023 01:34

Having the same issue, crashes within 30 seconds of entering play mode every single time, impossible to work. Also consistently crashes in player after build. Doesn't crash in parallels running a windows build
TrialByFun

Mar 16, 2023 15:26

Yeah just to add to the other comments. I'm getting this crash multiple times a day, sometimes multiple times per hour. I've stopped reporting it because it gets pinged back as a duplicate ( understandably ) but that's not to say it's not happening every day... just I'm not reporting it any more. i've been checking the Known issues list from each weekly version update for over a month now, but obviously it's still there. Are there any workarounds??
floatingfactory

Mar 15, 2023 23:15

Still happening on Unity 2022.2.11 and on an Intel Mac