Search Issue Tracker
In Progress
Fix In Review for 2021.3.28f1
Fixed in 2022.3.3f1, 2023.1.1f1, 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
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
Add comment