Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.51f1
2022.3.61f1
6000.0.48f1
6000.1.1f1
6000.2.0a10
6000.3.0a1
Issue ID
UUM-103999
Regression
No
Full stack trace is always printed when an exception occurs in an IL2CPP build
How to reproduce:
1. Open the attached “IN-97878” project
2. Select “File → Build And Run”
3. Observe the Player once the build is completed
Expected result: The displayed stack trace in the Player window is short (~4 lines)
Actual result: The full stack trace is displayed in the Player window (~15 lines)
Reproducible in: 2021.3.51f1, 2022.1.0a1, 2022.3.61f1 (e6a1f07378cd), 6000.0.48f1, 6000.1.1f1, 6000.2.0a10
Reproducible on: Windows 10 (by user), Windows 11
Not reproducible on: No other environments tested
Notes:
- The stack trace can also be seen in the Player log. Information about where to find it is found here: https://docs.unity3d.com/6000.0/Documentation/Manual/log-files.html
- Not reproducible with Mono scripting backend
- Not reproducible in the Editor
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Truncating the stack trace can have many un-intended consequences resulting in a high chance of a serious regression