Search Issue Tracker
By Design
Votes
0
Found in
2022.3.64f1
6000.0.52f1
6000.1.11f1
6000.2.0b9
6000.3.0a1
Issue ID
UUM-110855
Regression
No
Inner and outer exceptions are not unrolled correctly
How to reproduce:
1. Open the “ExceptionLayersBug.zip” project
2. Open the “SampleScene“
3. Enter Play Mode
4. Observe the Console
Expected result: Exceptions are logged in a callstack-like sequence ("A human-friendly..." → "Exception inside...” → "Arcane details about...")
Actual result: Exceptions are logged in the same sequence they are placed in the script ("Arcane details about..." → "Exception inside...” → "A human-friendly...")
Reproducible in: 2022.1.0a1, 2022.3.64f1, 6000.0.52f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a1
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Note: The comparison between the expected and actual result was made on a C# console project on Visual Studio 2022
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note:
Changing how exceptions are logged is not something we can change without it possible breaks peoples CI and automation. They might be people that rely on the current unfortunately illogical ordering.