Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.41f1
2021.3.15f1
2022.1.23f1
2022.2.0f1
2023.1.0a20
2023.2.0a1
2023.3.0a3
Issue ID
UUM-16617
Regression
No
Editor crash on "Transform::UpdateTransformAccessors" when exiting Play mode after recompiling scripts
How to reproduce:
1. Open the attached project
2. Play the "Init" scene
3. LMB through "English", "Initializing", "New Game 0", "Loading completed"
4. Once in the game, open the _Scripts folder and reimport any script to force a recompile
5. After a recompile, null reference exceptions will start flooding the console. Wait until there are ~ 300 of them and exit Play mode
6. Observe the crash (if it doesn't crash, go to step 2)
Reproducible with: 2020.3.41f1, 2021.3.15f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a20
Notes:
- It does not always reproduce on the first try
- Waiting for a larger number of null references exceptions to be thrown seems to help reproducing the crash a bit more consistently
- Having the Editor in full screen may increase the chance to reproduce
- When the Editor is paused due to null exception errors spam click the Step button and then quickly stop the Play Mode
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
- Polygons are created on the opposite side of the Sprite when the Sprite boundaries are above the edge of the Texture
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices in "com.unity3d.player.UnityPlayerActivity/2D Colour Attachement"
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
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.