Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2021.3.26f1
2022.3.1f1
2023.1.0b19
2023.2.0a18
2023.3.0a3
Issue ID
UUM-37747
Regression
No
Crash on -[IOGPUMetalDeviceShmem initWithDevice:shmemSize:shmemType:].cold.6 when Editor renders 3D objects in the Play Mode
Reproduction steps:
1. Open the attached project “CrashRepro”
2. Enter the Play Mode
3. Press “Start”
4. Wait a few seconds and press on the circles visible in the Play Mode
Expected result: The Play Mode continues
Actual result: Editor crashes
Reproducible with: 2021.3.26f1, 2022.3.1f1, 2023.1.0b19, 2023.2.0a18
Reproducible on: macOS 13.3.1 (Intel and M1 Max), Win 10
Note: on Intel Mac and Windows 10 the Editor freezes, on M1 Max Mac the project crashes
See comments for callstack
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the issue was identified as coming from user code. A workaround was identifed for the reproduction project.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2023.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the issue was identified as coming from user code. A workaround was identifed for the reproduction project.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.