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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
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