Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2022.1.X
Votes
0
Found in
2019.4
2020.3
2021.1
2021.1.22f1
2021.2
2022.1
Issue ID
1371478
Regression
No
Error is thrown when converting a GlobalObjectId to an Object reference and the Object is in an unloaded Scene
Reproduction steps:
1. Open the attached project ("GlobalIdBug22.1.0a13.zip")
2. Drag SceneA and SceneB_(To unload) to the Hierarchy window
3. Select GlobalIdBug under SceneA in the Hierarchy window
4. Open the context menu of the Script Component in the Inspector window and click "Get GlobalObjectId"
5. Unload SceneB_(To unload)
6. Select GlobalIdBug under SceneA in the Hierarchy window
7. Open the context menu of the Script Component in the Inspector window and click "Log GlobalObjectId"
8. Observe the Console window
Expected result: "GlobalObjectId is not found" is logged in the Console window
Actual result: "GlobalObjectId is not found" is logged in the Console window and an error is thrown:
Assertion failed on expression: 'manager != NULL'
UnityEditor.GlobalObjectId:GlobalObjectIdentifierToObjectSlow (UnityEditor.GlobalObjectId)
Reproducible with: 2019.4.32f1, 2020.3.21f1, 2021.1.27f1, 2021.2.0b17, 2022.1.0a13
Notes: Removing SceneB_(To unload) and repeating step 7 will not throw the error
Comments (1)
-
LazloBonin
Dec 14, 2021 04:39
Will this be backported to 2020.3 LTS like the other GlobalObjectId fixes?
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
- Crash on [NSApplication endModalSession:] when saving while Play Mode is loading
- Incorrect Preferred Height calculation when a single text line uses different Font Assets
- [ShaderGraph] Redo Collapse Nodes action does not fully collapse the Nodes
- [Ubuntu] Mouse cursor is set box select mode after exiting VFX Graph's Rename Context function
- Unrecognized identifier DECLARE_STACK_CB error is thrown when VirtualTexture Property is used with Custom RenderTexture target
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a1
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b2