Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.3.1f1
Issue ID
766939
Regression
No
[DestroyImmediate] Calling GetComponent after DestroyImmediate crashes at MonoBehaviour::CallAwake
Steps to reproduce:
1. Open attached project "766939.zip"
2. Open scene "A"
3. Run scene
Unity crashes
Workaround: Don't call GetComponent after DestroyImmediate OR change DestroyImmediate to Destroy
Reproduced with: 5.1.4f1, 5.2.4f1, 5.3.2p1, 5.4.0b4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Rigged GameObject doesn’t return to its idle state when disabling "Preview" and the GameObject has nested rigged GameObjects
- Error "ArgumentException: Trying to use an invalid resource" when creating custom post-processing effect in URP
- [DX12] GameObjects using CommandBuffer DrawProcedural and DispatchCompute calls have color flicker when changing color and moving mouse cursor
- The Player becomes unresponsive after resolution switch in Exclusive Fullscreen mode when using DX12 Graphics API
- (Apple Silicon) Floating point inconsistencies between mono and il2cpp
Add comment