Search Issue Tracker
Fixed in 2020.3.48f1
Fixed in 2020.3.X, 2021.3.X, 2021.3.25f1, 2022.2.X, 2023.1.X, 2023.2.X
Votes
0
Found in
2020.3.45f1
2021.3.18f1
Issue ID
UUM-26705
Regression
No
[Linux][IL2CPP] Player crash call stack is not displayed when the build is run with "-batchmode -nographics" arguments
Reproduction steps:
1. Open the attached “BugRepro” project
2. Click File > Build
3. Open the terminal and change the directory to build the folder
4. Run the executable with -batchmode -nographics arguments
Expected result: Call stack is properly displayed
Actual result: There is no call stack
Reproducible with: 2020.3.45f1, 2021.3.18f1
Couldn’t test with: 2022.2.0a1 (Couldn’t downgrade), 2022.2.6f1, 2023.1.0b4, 2023.2.0a2 (Didn’t crash)
Reproducible on: Ubuntu 20.04
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment