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
- [IL2CPP][Android] Incorrect symbol length/symbols returned with "AndroidJavaClass"and "AndroidJavaProxy" on Android < 5.1.1
- Animating the alpha channel of a color in a material causes the RGB channels to be reset to 0
- [Mobile] TouchScreenKeyboardType is missing DecimalPad
- Memory leak in Scene Memory/RenderTexture when Scene View is active and 'Animated Materials' + 'Post Processings' toggles are on
- Ctrl + F should start search in PackageManager
Add comment