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
- Character spacing value is not applied when using a specific font asset
- [Android][IL2CPP] Player crashes on __memcpy_aarch64_simd+276 when invoking native code via a plugin on some ARM64 Android devices
- [Android]Resources fail to load when the AAB build contains a large Addressables Bundle
- Unity is loading internal version of SharpZipLib instead of local version
- The Context Menu items are ordered incorrectly
Resolution Note (fix version 2020.1):
Fixed in 2021.2.0a7. Fixed exceptions getting logged in some cases where logEnabled is set to false.