Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.40f1
Issue ID
UUM-75125
Regression
No
[2021.3 only] Crash on Transform_CUSTOM_set_localScale_Injected when opening a Prefab that contains a script calling set_LocalScale during serialization
Reproduction steps:
1. Open the attached “ReproProj” project
2. Open the “Assets/Game/Prefabs/House.prefab“ Prefab
Expected result: The Prefab Mode is opened
Actual result: The Editor crashes
Reproducible with: 2021.3.40f1, 2022.1.24f1
Not reproducible with: 2022.2.0a1, 2022.3.37f1, 6000.0.10f1
Reproducible on: Windows 10, macOS 14.5 (M1 Max)
Not reproducible on: No other environment tested
First few lines of the stack trace:
#0 0x00000100c69e2c in Transform::SetLocalScale(Vector3f const&)
#1 0x000001002f5000 in Transform_CUSTOM_set_localScale_Injected(ScriptingBackendNativeObjectPtrOpaque*, Vector3f const&)
#2 0x0000035d29b360 in (wrapper managed-to-native) UnityEngine.Transform:set_localScale_Injected (UnityEngine.Transform,UnityEngine.Vector3&) [{0x3405878f0} + 0x78] (0x35d29b2e8 0x35d29b3d0) [0x16b802a80 - Unity Child Domain]
#3 0x0000035d29b28c in UnityEngine.Transform:set_localScale (UnityEngine.Vector3) [{0x3405877e0} + 0x24] (0x35d29b268 0x35d29b298) [0x16b802a80 - Unity Child Domain]
#4 0x0000035d299e90 in HouseDimensions:SetDimensions ()
#5 0x0000035d299bdc in HouseDimensions:OnAfterDeserialize ()
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
- Material Component has two horizontal lines under it when its foldouts are closed
- Some selected Mesh Renderer Materials lead to Assets folder when pinged
- Editor colors appear darkened out when HDR Display Output is enabled
- Default Mesh Renderer Material cannot be found in the Select Material window after removing it from the GameObject
- UI Builder button text disappears in the GameView when the radius of the button is increased in a specific project
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.