Search Issue Tracker
Fixed in 2020.3.40f1
Fixed in 2022.2.0b4
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.3.40f1):
Fixed by another internal issue: UUM-1595: PrintStackTraceLinux frequently crashes
Resolution Note (fix version 2022.2.0b4):
Fixed by another internal issue: UUM-1595: PrintStackTraceLinux frequently crashes