Search Issue Tracker
Third Party Issue
Votes
5
Found in
2020.3.40f1
2021.3.7f1
2022.1.12f1
2022.2.0b3
2023.1.0a4
Issue ID
UUM-10411
Regression
No
[M1][Rosetta] Editor crashes on mono_arch_patch_callsite when entering the Play Mode
Reproduction steps:
1. Open the user’s attached project
2. Enter the Play Mode
Expected result: Editor enters Play Mode
Actual result: Editor crashes
Reproducible with: 2020.3.40f1, 2021.3.7f1, 2022.1.12f1, 2022.2.0b3, 2023.1.0a4
Reproducible on: MacOS 12.5 (M1 Max)
Notes:
If Editor doesn’t crash when entering the Play Mode, exit and enter it until Editor crashes. (~10-20% reproduction rate)
Reproducible with Rosetta.
First lines of Stack Trace:
#0 0x00000162f0225b in mono_arch_patch_callsite
#1 0x00000162eaf535 in common_call_trampoline
#2 0x00000162eaec37 in mono_magic_trampoline
#3 0x00000159185396 in (Unknown)
Comments (1)
-
messhias
Aug 25, 2022 09:39
This, unfortunately, happened with me again yesterday and all my game objects are gone and I have to start creating my whole scene again :(
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "GetPreferedValue" returns max value when using auto-sizing
- UI Builder doesn't update the style sheet when using "Extract inline style" right-click option
- “Assertion failed on expression” errors thrown when undoing Nodes creation with keyboard shortcut
- Crash on various stack traces when using Texture2D.CreateExternalTexture() while rendering
- Clicking on section text in Node Library > Context folder throws NullReferenceException errors
Resolution Note:
This crash is unfortunately a result of either a bug or an otherwise behavioral difference in the emulated rosetta environment. After investigating ourselves as well as consulting with the primary developer at Microsoft responsible for the jitting implementation in mono we were unable to come up with a solution to all of the crashes the sample project encounters.
An upstream bug was filed here: https://github.com/dotnet/runtime/issues/79557 and work is being done to address part of the issues that were discovered.
It is encouraged to run natively on the system architecture without emulation via rosetta as much as possible.