Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.3.0a10
Issue ID
1074324
Regression
No
[Linux editor] ForceCrash(ForcedCrashCategory.Abort) not being caught by crash reporter
-e: see title, crash reporter is not opening. it does so for all the other categories (AccessViolation, FatalError and PureVirtualFunction)
-repro:
--open attached project
--run sample scene
--click the crash button
--NOTICE the crash report doesn't come up
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2019.1):
Linux and Mac will now launch the BugReport crash handler when a SIGABRT is sent.