Search Issue Tracker
Active
Votes
0
Found in
2022.3.69f1
6000.0.63f1
6000.2.15f1
6000.3.0f1
6000.4.0a5
6000.5.0a2
Issue ID
UUM-128880
Regression
No
Mono Windows Builds don't produce full log callstacks when generating logs
How to reproduce:
1. Open the attached “MissingCallstacks” project
2. Build And Run the project
3. Press the Button with the “Debug Message!” text
4. Exit the game
5. Open File Explorer
6. Navigate to AppData > LocalLow > UnitySupport > MissingCallstacks > Player
7. Note the outputted logs
8. In the project go to Edit > Project Settings> Player > Configuration
9. Change the Scripting Backend from Il2cpp to Mono
10. Repeat steps 2-7
11. Observe the difference between the outputted logs
Actual result: Only the Il2cpp log has the callstack
Expected result: Both logs have the same callstack
Reproduces with: 2022.3.69f1, 2023.1.0a1, 6000.0.63f1, 6000.2.15f1 , 6000.3.0f1, 6000.4.0a5, 6000.5.0a2
Reproduces on: Windows 11
Not reproducible on: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment