Bug Unity apple silicon M1 version crashes very often

Hello,
I just bought an m1 mac and unity crashes super often when using the apple silicon version. Intel version is fine so far.

My question is: is there a way for me to check the crash report? When unity crashes, the window simply disappears. I'd love to contribute and create a bug report, but I can't really tell why exactly it's crashing (I'm just doing something in the editor and it just crashes when I press play, etc). Is there a way for me to check an error log of some kind?

 

same problem
in random moment its freezes. only restart helps. endless "loading" macos animation.

 

Same here, freezing almost 10+ times a day... have to force quit unity every time.

 

FYI it stopped crashing for me at version 2022.1.11f1

 

I am using version 12.6 Apple M1 mac mini and recently updated to Unity version 2021.3.11f1 and now I get the spinning wheel of death every time. Is this issue with M1's happening to others?

 

I'd recommend trying out the newest 2022 version if your problem persists.

 

I've tried updating to the 2022, but it looks like the problem is still there. Almost every time I go into play mode, I get the spinning wheel of death a few seconds in. Using M1 Macbook pro, Unity 2022.1.23f. It was also happening to me on the 2021 version, which is why I originally updated.

 

I'm on 2021.3.12f1 silicon LTS. I've had an M1 since late July and have always used LTS.
I've never had any significant problems. However, when in debug mode a long time with Visual Studio (hour+) and stopping play, I have gotten the nonstop spinning wheel, requiring force quit--probably another bug. Always a good idea to save before play.

Also I probably have had other problems when memory available was low, which is to be expected.

(edit for clarity)

 

Same to me on the 2020, found by Profiler, what it's have something with GC.MarkDependencies

 

On 2022.2.0b16, I can create a new project. Create a subscene, add a cube to the subscene, and press play. It will crash almost every time, and the times that it doesn't crash, if I stop and press play again, it always crashes. I have yet to be able to press play twice in a row without a crash, and I just have a single cube in the scene.

Is there a thread anyone can link where someone from Unity has responded?

 

Ok, I was being dumb and forgetting to NOT use the default material on the default cube, and instead I needed to use a material that I had converted to be compatible with URP... So this was my bad, though I wish making a new 3D URP project auto converted the materials.

 

this should not make unity crash though.

 

2022.2.1f Silicon crashes every time, after we run and wait a little while. Intel version so far does not crash.

 

Running the intel version solved it for me. 2022.2.5f1

 

I'm not sure it's 100% reproducible, but it happens very often for me: Manually hitting refresh (I have auto refresh off) when in Play mode, when I have made shader changes, results in the editor hanging on an M1, and I have to force close it.

There is no crash / bug reporter popping up when that happens.

 

It happens every 2-5 minutes on 2022.2.5-6.
When I paint the terrain with textures, moving objects, and playing levels. All the time, the callstack is always the same.
Today starting from 9:00 AM till now it crashes 18 times (yes, I'm counting). Now I'm trying to download the "Intel" version of the editor.

But, it is reported already by someone else:
https://issuetracker.unity3d.com/is...is-left-idle-while-the-editor-is-in-play-mode

Need more 9 votes.

 

Gave a vote, although I'm fairly sure Unity's attitude doesn't depend on the votes and it's generally more busywork for us to have an illusion of control over what happens with Unity.

 

I'm also getting a lot of crashes caused by URP (and HDRP too).
Not at the same frequency though. Since updating to 2022.2.4f1 most crashes caused by creating assets were gone so I'm only left with random crashes (not during Play mode, though I also noticed that even playing a build of an URP project can crash after a couple minutes)
There was a couple times where the editor crashes every 5 minutes, but usually it's once per 30/60 mins
I switched back to the built-in rp since it now supports shader graph and would you believe it, no crashes since

 

I'm getting plenty of crashes and I'm on built in. I feel like mine are related to Unity's UI, mostly. I don't doubt that things would be "crash-ier" with URP / HDRP though.

 

interesting. What version are you using ?
In my case it's definitely URP causing the crashes from the error log. Have been running built in for at least 10 hours last couple of days and had 0 issues

 

Latest (I think it's .18f1?) Silicon 2021 LTS

 

Some of the crashes were fixed in 2022.2.4f1 iirc.
Haven't tried 2021 lts so i dont know if those fixes made it there or not

 

Moved from 2022.2.6 Silicon to 2022.2.6 Intel version - no crashes during the 6 hours yesterday.
It works using Rosetta2 and it works noticeably slow than Silicon while entering Play mode, but building levels and the other stuff work just fine.
The only issue I have now is that OS/Android builds are constantly crashing.
Hope they fix this soon.

 

Same Problem here on the brandnew macbook pro M2.
Every 30 minutes or so I see the loading wheel of death and then I have to force close it.

Very annoying.

 

I have the same problem in builds....
Mac mini m2

 

Same problem. M2 Pro. Any fix for 2021.3 LTS version?

Also, there is no way to send a bug report for this because the editor just hangs with an infinite loading spinner. Have to force quit.

 

Same here, with MacBook Pro M2 Max. I frequently see the loading wheel of death and then I have to force close the editor.

 

Okay guys, Unity staff replied, without votes no one will help mac community.
Please everyone, go and vote
https://issuetracker.unity3d.com/is...is-left-idle-while-the-editor-is-in-play-mode

 

Hope we get a fix for this soon.
For someone who works fulltime with a company on a project that uses URP I find myself unable to make almost any progress and using intel builds is as slow as it gets. Kind of beats the purpose of getting a mac studio

 

For me using the Intel version above 2021.3.1.17, I'm unable to even load our project, it just hangs while loading.
This really needs a fix ASAP, Unity is almost unusable at this point.

 

Adding to the pile, I think I'm experiencing related crashes, Unity version 2022.2.5f1, running on M1 Pro.
Here's the beginning of my stack trace, if it can help...

Spoiler

Code (csharp):

1.  
2. -------------------------------------
3. Translated Report (Full Report Below)
4. -------------------------------------
5.  
6. Process:               Unity [9945]
7. Path:                  /Applications/Unity/*/Unity.app/Contents/MacOS/Unity
8. Identifier:            com.unity3d.UnityEditor5.x
9. Version:               Unity version 2022.2.5f1 (2022.2.5f1)
10. Code Type:             ARM-64 (Native)
11. Parent Process:        Unity Hub [8551]
12. Responsible:           Unity Hub [8551]
13. User ID:               501
14.  
15. Date/Time:             2023-02-27 13:44:59.8836 +0100
16. OS Version:            macOS 13.2.1 (22D68)
17. Report Version:        12
18. Anonymous UUID:        02227271-21D1-6C17-4F72-AC649CABB3AF
19.  
20. Sleep/Wake UUID:       13FBB110-087C-4C3D-A8C8-F653AB5D687B
21.  
22. Time Awake Since Boot: 68000 seconds
23. Time Since Wake:       14497 seconds
24.  
25. System Integrity Protection: enabled
26.  
27. Crashed Thread:        0  tid_103  Dispatch queue: com.apple.main-thread
28.  
29. Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
30. Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
31. Exception Codes:       0x0000000000000001, 0x0000000000000000
32.  
33. Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
34. Terminating Process:   Unity [9945]
35.  
36. VM Region Info: 0 is not in any region.  Bytes before following region: 4335894528
37.       REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
38.       UNUSED SPACE AT START
39. --->
40.       __TEXT                      102708000-1062dc000    [ 59.8M] r-x/r-x SM=COW  ...s/MacOS/Unity
41.  
42. Thread 0 Crashed:: tid_103 Dispatch queue: com.apple.main-thread
43. 0   libsystem_kernel.dylib                   0x181352280 __kill + 8
44. 1   libmonobdwgc-2.0.dylib                   0x2abe859e0 mono_chain_signal + 104
45. 2   libmonobdwgc-2.0.dylib                   0x2abdd1604 mono_sigsegv_signal_handler_debug + 548
46. 3   libsystem_platform.dylib                 0x1813b82a4 _sigtramp + 56
47. 4   Unity                                    0x103313dd4 GfxDevice::ExecuteAsync(int, void (*)(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*), GfxDeviceAsyncCommand::ArgScratch**, GfxDeviceAsyncCommand::Arg const*, JobFence const&) + 80
48. 5   Unity                                    0x103313dd4 GfxDevice::ExecuteAsync(int, void (*)(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*), GfxDeviceAsyncCommand::ArgScratch**, GfxDeviceAsyncCommand::Arg const*, JobFence const&) + 80
49. 6   Unity                                    0x102fad9e0 ScheduleRenderJobs(unsigned int, ScriptableRenderLoopShadowsArg const*, JobFence const&) + 568
50. 7   Unity                                    0x102fad5e8 ExecuteDrawShadowsCommand(SlicedDrawShadow const&) + 880
51. 8   Unity                                    0x102fb34f4 ScriptableRenderContext::ExecuteScriptableRenderLoop() + 1312
52. 9   ???                                      0x35c38ba7c ???
53. 10  ???                                      0x35c38b96c ???
54. 11  ???                                      0x35c38b8a8 ???
55. 12  ???                                      0x3586c502c ???
56. 13  ???                                      0x37bedd0f0 ???
57. 14  ???                                      0x358696f04 ???
58. 15  ???                                      0x358695ea4 ???
59. 16  ???                                      0x35859b5c0 ???
60. 17  ???                                      0x35859ba6c ???
61. 18  libmonobdwgc-2.0.dylib                   0x2abdd48a4 mono_jit_runtime_invoke + 1924
62. 19  libmonobdwgc-2.0.dylib                   0x2abf5b45c do_runtime_invoke + 104
63. 20  libmonobdwgc-2.0.dylib                   0x2abf5b37c mono_runtime_invoke + 100
64. 21  Unity                                    0x1034132b8 scripting_method_invoke(ScriptingMethodPtr, ScriptingObjectPtr, ScriptingArguments&, ScriptingExceptionPtr*, bool) + 88
65. 22  Unity                                    0x1033f24c4 ScriptingInvocation::Invoke(ScriptingExceptionPtr*, bool) + 164
66. 23  Unity                                    0x102fb4934 ScriptableRenderContext::ExtractAndExecuteRenderPipeline(dynamic_array<Camera*, 0ul> const&, void (*)(SceneNode const*, AABB const*, IndexList&, SceneCullingParameters const*), void*, ScriptingObjectPtr) + 516
67. 24  Unity                                    0x102dbae10 RenderManager::RenderCamerasWithScriptableRenderLoop(int) + 528
68. 25  Unity                                    0x102dbb220 RenderManager::RenderCameras(int, void (*)(), void (*)()) + 64
69. 26  Unity                                    0x103e6dd70 RepaintController::RenderPlayModeViewCameras(RenderTexture*, int, Vector2f, bool, bool) + 576
70. 27  Unity                                    0x1043808b8 EditorGUIUtility::RenderPlayModeViewCamerasInternal(RenderTexture*, int, Vector2f, bool, bool) + 28
71. 28  Unity                                    0x102ab6fa4 EditorGUIUtility_CUSTOM_RenderPlayModeViewCamerasInternal_Injected(ScriptingBackendNativeObjectPtrOpaque*, int, Vector2f const&, unsigned char, unsigned char) + 372

PS: @Tautvydas-Zilys you've got such a patience I for one really appreciate it. You're one against thousands!

 

And, I have to say, this:

actually worked!
It's a bit annoying that I cannot use the Frame Debugger (apparently it requires multithreaded rendering!), but at least I can work.
On a side note, I was having FREQUENT crashes while using Frame Debugger, so it all makes sense... it's handy in case you want to trigger the crash easily for reproduction

 

I know this might be kind of annoying but could someone explain how you start the editor with -force-gfx-st and what it means?
I'm a bit new to all this, but these crashes are really impeding my progress.
Thanks in advance!

-EDIT-
I figured it out and it seems to have stopped the crashes. Thank god.

 

I had editor crashes like every 5-10 minutes on the 16" M1 Pro Macbook with the 2022.2.6f1 and newer. I also had the freeze where I had to kill the editor a lot, paired with proper crashes.

After adding -force-gfx-st it didn't crash once. Probably should be working without "hacks" like this but this is the first time in 2023 I feel like I am using a stable product

 

HOW do you "add" -force-gfx-st when running Unity?

C'mon guys, don't just say you figured it out without sharing what you figured out

 

You can add them via the hamburger menu for projects in unity hub

 

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

 

For me, 2022.2.9 is more unstable than 2022.2.8.
On my current project, it crashes after ~15 seconds each time i open my project. But this time w/o invoking the Crash Reporter. The editor just suddenly closed.
I decided to start the new project (3D core), adding terrain, skybox, and a small number of objects. But during the 1-2 hours of working it constantly crashes. This time with the Crash Reporter. All the time i see this:

Code (csharp):

1.  
2. #0 0x000001048e7104 in ScriptableRenderLoopJob(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*)
3. #1 0x00000104c2b1d8 in GfxDevice::ExecuteAsync(int, void (*)(GfxDeviceAsyncCommand::ArgScratch*, GfxDeviceAsyncCommand::Arg const*), GfxDeviceAsyncCommand::ArgScratch*{*}, GfxDeviceAsyncCommand::Arg const{*}, JobFence const&)
4.  

I found that there is one bug reported with the same crash log, however, that bug is happening when you left the editor idle. But mine happens during work. I've tried to register mine, but it was closed as a duplicate.

 

Thanks a lot for the update, @robinDMUnity! Just to clarify...

Are you saying that we should have Graphic Jobs (Experimental) set to ON? (in Project Settings > Player > Other Settings).

I've had a lot of crashes before even while not in Play Mode and for me, starting the editor with -force-gfx-st helped. But I do still get some crashes while in Play Mode... I'll try enabling that option. Are they two issues though?
I'm confused that I'm starting the editor to be single-threaded rendering, but then enabling an option called Graphic Jobs.

I also get the spinning loading icon sometimes, but more rarely. I'll submit reports with the project.

(and yes, Silicon M1 Mac here)

 

I've been using 2021.3.20 targeting tvOS with no problems, but today I opened a project in 2022.1 on my M2 Max, targeting Android, and it just keeps crashing. This Unity project had no issues on my previous mac (intel).

 

My game build is still crashing on Apple M1\M2. Unity 2022.2.10f. I tried enabling Graphic Jobs (Experimental), but it only makes the game Freezee on a change of scene.

Game runs great if I build it on 2021 LTS, but that's not an option for me, please fix 2022 already!

 

For whoever is having issues with a build, I would suggest to launch the game via the terminal with the

-force-gfx-direct

argument. The full command:

open AppName.app --args -force-gfx-direct

Notice: the build needs to be a Development build to be able to launch it with the argument (afaik).

For the editor it's a different argument as mentioned before. I launch it with

-force-gfx-st

adding the argument directly from within the Unity Hub.

 

I tried to add that as launch argument in steam, but game is still crashing. So this is not a solution to the problem

 

Hi there,
I'm now on Unity 2022.2.10 with -force-gfx-st and Unity Editor itself is stable as hell on my Studio M1 Max. 4 hours, with no crashes or deadlocks.
Yesterday, I spent over 9h on 2022.2.10 without that arg, and it crashed two times, and two times I got the deadlock.
But.....
The project I'm working on was created about 2 years using Unity 2020 (don't remember the exact number), then it was upgraded to 2021 and then after a while moved to 2022.1 (beta), and then back to 2021 when 2021 becomes LTS. And then upgraded back to 2022 on September 2022. So, this project had some beta packages, which were removed (not sure if completely removed, or if some parts of them are still there). There were some experiments, tried a lot of packages for vegetation, trees, etc... Plus, some packages were replaced by another package. So, I think the project was too garbaged. There were a lot of unsupported shaders.
Now, I created a brand new project, and imported really needed assets/packages/scripts.
And now, everything works nicely and cleanly.
So, now, I'm not sure if all these instabilities were due the Unity or the project garbage i had.
But now all looks stable.

-A.

 

Ok so I've been encountering this hanging issue that requires a force quit. I added -force-gfx-st to my options and I've now discovered a new bug...

With that option enabled, vsync settings in the editor game mode doesn't work at all. I'm getting uncontrollable 300+ FPS and it's turning my Macbook into a rocket.

Application.targetFrameRate works but still turns my macbook into a rocket for some reason. I'm guessing it's because one physical core of the SoC is doing all the processing?

Edit: Yeah there's a really annoying bug with forcing single threaded rendering. Even on non demanding scenes (read: entirely empty scenes) the CPU fan goes to 100%, VSync doesn't work. Target frame rate doesn't affect the fans at all, they still speed up to 100%.

 

It might be because the build is not a Development build? I forgot to mention that. I've added it to my post, for clarity.

 

What's the status on this? Running 2021.3.21f1 and it's still unstable as hell. Sometimes immediately freezes during startup even.