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
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
- UnityEvent does not get pasted to a uGUI component when trying to copy it from a Script
Resolution Note (fix version 2019.1):
Linux and Mac will now launch the BugReport crash handler when a SIGABRT is sent.