Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.11f1
Issue ID
UUM-66146
Regression
No
Crash on ResolveInstanceIDMapping when building the Player on a specific machine
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Build and Run the Player (File > Build And Run)
3. Observe the Player
Expected result: The Editor does not crash
Actual result: The Editor crashes
Reproducible with: 2021.3.11f1
Reproducible on: Windows 10 (user's), Windows 11 (user’s)
Not reproducible on: macOS Sonoma 14.3.1 (Intel), Windows 10 Enterprise 21H2
Notes:
- The issue could not be locally reproduced by the CQA
- The user’s reported findings:
a crash occurs regardless of the selected build platform
a crash occurs on both the 2021.3 & 2022.3 LTS versions
a blank project builds correctly
reinstalling both Unity and Windows did not solve this issue
First few lines of the stack trace:
0x00007ff60c23a7a2 (Unity) ResolveInstanceIDMapping
0x00007ff60c225dd9 (Unity) BuildingPlayerOrAssetBundleInstanceIDResolveCallback
0x00007ff60ae0d8f9 (Unity) TransferPPtr<StreamedBinaryWrite>
0x00007ff60ccd9eae (Unity) AnimatorController::TransferRuntimeData<StreamedBinaryWrite>
0x00007ff60b592f0b (Unity) SerializedFile::WriteObject
0x00007ff60b57c91b (Unity) PersistentManager::WriteFile
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
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.