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
- Runtime theme's text color and font-size cannot be overridden from user stylesheets using :root selector
- Serialized attribute cannot be focused and written in when it goes after "TextArea" field
- Crash when dragging Prefab into scene
- DrawMeshInstancedProcedural is using only baked Reflection Probes Cubemaps when Forward Rendering Path is used
- Setting the Camera.targetTexture through a script will cause the depth buffer to start clearing between camera renders
Resolution Note (fix version 2019.1):
Linux and Mac will now launch the BugReport crash handler when a SIGABRT is sent.