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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
Add comment