Search Issue Tracker
Fixed in Unity 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
- Unable to find a corresponding location while using Partial classes/methods when debugging
- Crash in AnimatorOverrideController::GetOriginalClip when using an indexer operator to access an animation clip
- Import errors when converting from Blend to FBX
- [WebGL] In developer build method Mathf.CeilToInt() throws an exception
- [Tilemap] Visualization of the tile is created in another tile when quickly moving cursor after releasing left mouse button
Add comment