Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2019.1.X
Votes
0
Found in
2018.3.0b5
Issue ID
1093869
Regression
No
Crash on object:runtime_invoke_void__this__ after calling Null.Equals inside Try statement and Debug.Log in Finally statement
How to reproduce:
1. Open the "Try_Crash_Repro.zip" project
2. Open the "SampleScene.unity"
3. Press Play
Actual result: Unity crashes.
Reproducible with: 2019.1.0a10, 2019.1.0a1, 2018.3.0b11, 2018.3.0a1, 2018.2.16f1, 2018.2.0a1, 2018.1.9f2, 2018.1.0a1, 2017.4.16f1.
Notes:
The crash is ONLY reproducible if:
1. There is no catch { } section.
2. There is Debug.Log() in the Finally { } section.
3. There is String.Equals() inside the Try { } section and the String is Null.
------------------------------
Fixed in 2019.2.0a3, 2019.1.0b3, 2018.3.5f1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] PointerEventData.pointerId value is incorrect when pressing a finger on the screen
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
Add comment