Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.3.X, 2022.1.X
Votes
0
Found in
2020.3.31f1
2021.2
2022.1
2022.2
Issue ID
1411374
Regression
Yes
[Mac] Stack trace is not available after a crash in the Editor log
Steps to reproduce:
1. Open the attached project
2. Enter Play mode in SampleScene
3. After the project crashes, check Editor log
Expected result: the log contains information about the crash and the stack trace
Actual result: there is no information about the crash and no crash log
Reproducible with: 2021.2.16f1, 2021.2.0a19, 2022.1.0b13, 2022.2.0a8
Not reproducible with: 2019.4.37f1, 2020.3.31f1, 2021.2.0a17
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 2022.2):
Fixed issue where callstacks would not resolve on OSX
Fixed in 2022.2.0a13
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.1f1
Resolution Note (fix version 2021.3):
Fixed in 2021.3.4f1.243