Search Issue Tracker
Fixed
Fixed in 2020.3.48f1, 2021.3.25f1, 2022.2.21f1, 2023.1.0b16, 2023.2.0a10
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
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
Add comment