Search Issue Tracker
Won't Fix
Votes
3
Found in
5.6.1f1
Issue ID
921666
Regression
No
Crash on GameObject::WillDestroyGameObject after Destroy() and Application.LoadLevel() methods
How to reproduce:
1. Open attached Unity project "Sergio_Almodovar.zip"
2. Build game
3. Play the game
4. Collide with an enemy (white ball)
Expected result: After players collision with an enemy and destroying player scene reloads without crash.
Actual result: Game crashes after destroying players object and loading level.
Reproducible with: 2017.2.0a3, 2017.1.0b9, 5.6.1p4, 5.5.4f1
Notes:
- In 5.5.4f1 version crash occurs after pressing "Start" in the game.
- Destroy() and Application.LoadLevel() methods located in Assets --> Scripts --> Movement.cs script.
Comments (2)
-
Disastercake
Jul 30, 2018 01:48
Anyone ever find a work around for this? It's completely blocking me from working on my game at this point. Frustrating, to say the very least.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.