Search Issue Tracker

Fixed in Unity 2019.1

Votes

0

Found in

2018.3.0a10

Issue ID

1074324

Regression

No

[Linux editor] ForceCrash(ForcedCrashCategory.Abort) not being caught by crash reporter

Linux

-

-

Priority: 2Necessary for shipping a final release

-

Severity: 3Secondary functionality broken

-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

Response avatar

Resolution Note:

Linux and Mac will now launch the BugReport crash handler when a SIGABRT is sent.

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.