Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2018.4
2019.4
2019.4.18f1
2020.2
2021.1
2021.2
Issue ID
1316677
Regression
No
[Core] UnitySynchronizationContext shouldn't call Debug.Log directly when catching exceptions
How to reproduce:
1. Open attached project "StartException" and scene "SampleScene"
2. In Project window, open and observe Assets/TestScript.cs
3. Enter Play Mode
4. Observe Console window
Expected result: Exception is logged
Actual result: No exception is logged
Reproducible with: 2018.4.32f1, 2019.4.21f1, 2020.2.6f1, 2021.1.0b9, 2021.2.0a6
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
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
- Unity Version Control server textfield’s text overlaps with the dropdown triangle button in the Explore repositories window when an organization with a long name is selected
Resolution Note (fix version 2020.1):
Fixed in 2021.2.0a7. Fixed exceptions getting logged in some cases where logEnabled is set to false.