Search Issue Tracker
By Design
Votes
0
Found in
2021.3.27f1
2022.3.3f1
2023.1.1f1
Issue ID
UUM-40476
Regression
No
Crash on BackupState::MemoryIDToFileID::operator() when entering Play Mode
How to reproduce:
1. Open the attached project "VR_2023_II.zip"
2. Enter Play Mode
Reproducible with: 2021.3.27f1, 2022.3.3f1, 2023.1.1f1
Could not test with: 2023.2.0a20 (compilation errors in the Console window)
Reproducible on: Windows 10
First few lines of the stack trace:
0x00007FFFF8456C10 (Unity) strncmp
0x00007FFFF5EDFF3A (Unity) BackupState::MemoryIDToFileID::operator()
0x00007FFFF5EF7D71 (Unity) IterateTypeTreeEx<IterateTypeTreeFunctorAdaptorBackupState::MemoryIDToFileID >
0x00007FFFF5F03A17 (Unity) SerializableManagedRefTransfer::Transfer<SerializableManagedRefBackupGenerator>
0x00007FFFF5FFC584 (Unity) SerializedFile::WriteObject
0x00007FFFF5FE6543 (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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Unity does not allow attaching a ScriptableObject to a Game Object. This is the reason why entering play mode crashes with the attached repro project. The UpdateData derives from a ScriptableObject and is attached to a game object.