Search Issue Tracker
Fixed in 2021.3.28f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0a17
Votes
0
Found in
2020.3.48f1
2021.3.25f1
2022.2.20f1
2023.1.0b17
2023.2.0a15
Issue ID
UUM-35527
Regression
No
[Entities][Linux][IL2CPP] Player crash stack trace is displayed multiple times 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: Crash stack trace is displayed only one time
Actual result: Crash stack trace is displayed either with each of the lines duplicated or the entire stack trace displayed multiple times
Reproducible with: 2020.3.48f1, 2021.3.25f1, 2023.1.0b17, 2023.2.0a10, 2023.2.0a15
Couldn’t test with: 2020.3.47f1, 2021.3.23f1, 2022.2.20f1, 2023.1.0b15, 2023.2.0a10 (UUM-26705: call stack is not displayed at all)
Reproducible on: Ubuntu 22.10
Note: When testing this issue, the UUM-26705 fix for the 2022.2 stream has not yet come out, but this issue will probably be reproduced there.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
Add comment