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
- [iOS] SystemInfo.systemMemorySize returns negative values
- Crash on PAL_LocalIPC_IsConnected when IPC fails on launch
- [Profiler] Only the first frame gets highlighted in the CPU Usage chart when selecting samples in the Hierarchy
- [UWP] Builds fail with Rewired
- [macOS] Video Player's 5.1 audio channel layout is incorrect when outputting to Audio Source
Add comment