Search Issue Tracker
Fixed
Votes
0
Found in
2022.2.0a15
Issue ID
UUM-462
Regression
Yes
[Linux] Editor.log doesn't have a stack trace after the crash
Reproduction steps:
1. Create an empty project
3. Create a new Script and add "Utils.ForceCrash(ForcedCrashCategory.Abort);" to Start()
3. Attach the scrip to any Object in the scene
4. Enter play mode
5. After the crash, check Editor.log
Expected result: Editor crashes and the Stack Trace is displayed at the end of the Editor.log
Actual result: Editor crashes, but there is no Stack Trace at the end of the Editor.log
Reproducible with: 2022.2.0a11, 2022.2.0a15
Not reproducible with: 2021.3.3f1, 2022.2.0a10
Reproducible on: Ubuntu 20.04
Not reproducible on: Windows 10, 11, MacOS 12.3.1 (M1 Max)
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
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
- Group Node name text is way smaller in the renaming state than the actual display size
Resolution Note:
Fixed by another internal issue: UUM-1595: PrintStackTraceLinux frequently crashes