Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.2.X
Votes
0
Found in
2017.4.0f1
2017.4.23f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1142726
Regression
No
Application.ForceCrash/Utils.ForceCrash not all ForcedCrashCategories produce a crash
Steps to reproduce:
1. Open user attached project
2. Build & Run
3. Check all 4 buttons and observe that not all of them produce a crash
Expected result: Application.ForceCrash/Utils.ForceCrash all ForcedCrashCategories should produce a crash
Reproduced in:
2019.2.0a11, 2018.3.12f1 - Application.ForceCrash();/Utils.ForceCrash() only button 1(ForcedCrashCategory.FatalError) does not crash the editor
2017.4.25f1, 2017.4.3f1 - Application.ForceCrash(); button 0 freezes the editor(logcat shows that crash occured), button 1 and button 3 does not crash
2017.4.0f1, 2017.4.2f2 - Application.ForceCrash(); button 1 and button 3 does not crash
Reproduced testing on Android, Windows Standalone and Editor
Devices under test:
VLNQA00025, Xiaomi Mi 5s (MI 5s), Android 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00117, Google Pixel 2 (Pixel 2), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash when attempting to create a custom FMOD DSP unit
- [Linux] Floating windows do not keep their size after restarting the Editor
- .framework plugin is mistakenly treated as a directory when building for Universal Windows Platform
- Artifacts appear on GameObjects when using the WebGL Player on Silicon macOS
- Only the icon of the disabled child GameObject is faded when a parent GameObject is a Prefab
Add comment