Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.41f1
2021.3.14f1
2022.1.23f1
2022.2.0f1
2023.1.0a19
Issue ID
UUM-22433
Regression
No
Editor crashes on UnityEngine.GameObject:get_transform after clicking the GameObject that was used in building Adressables
How to reproduce:
1. Open the user-attached project “TestNonRecursiveBuild”
2. Click Window -> Asset Management -> Addressables -> Groups
3. Click Build -> Clear Build Cache -> All
4. Click Build -> New Build -> Default Build Script
5. Select Assets/Cube.prefab
6. Uncheck Adressable in the Prefab inspector
7. Rebuild the Addressables (Step 4)
8. Open the “SampleScene” scene and enter the Play Mode
9. Click on the button in the Game View, then select “GameObject” in the Hierarchy and double-click “Cube” in the Inspector
Expected result: The Editor didn’t crash
Actual result: The Editor crashed
Reproducible with: 2020.3.41f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a19
Reproducible on: Windows 11 Pro
First few frames of the stack frames:
0x000001e3de8f1d31 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.GameObject:get_transform (UnityEngine.GameObject)
0x000001e3de8f0d73 (Mono JIT Code) UnityEditor.GameObjectInspector:CalculatePrefabStatus ()
0x000001e3de8f064b (Mono JIT Code) UnityEditor.GameObjectInspector:OnEnable ()
0x000001e46a1d6428 (Mono JIT Code) (wrapper runtime-invoke) object:runtime_invoke_void_{_}this{_}_ (object,intptr,intptr,intptr)
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
- TileMap Palette preview flickers when scaled
- ShaderGraph Blackboard "plus" sign is not centered within the button
- [URP] When Rendering Layers are enabled, the DepthNormalPrepass is enabled even if not used
- Shader Graph Asset icon is blurry in the 4K monitors
- Default Value of ShaderGraph Color property is 0 by default
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.