Search Issue Tracker
Fixed in 2019.1
Votes
14
Found in
5.3.0f4
Issue ID
753944
Regression
No
Assigning a custom Debug.logger.logHandler doesn't intercept thrown exceptions
To reproduce:
1. Open project
2. Press play
Notice that the "Test" class intercepts Debug.Log and Debgu.LogException, but doesn't intercept the exception it throws.
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
- HDR values are not taken into account when using baked gradient environment
- [Asset Importer] Custom framerate error should only be logged when frame rate is used
- 'NullReferenceException' is thrown when selecting multiple Particle Systems with Texture Sheet Animation module expanded
- Particle System with Texture Sheet Animation has a different playback speed from an Animation clip when using "FPS" Time Mode
- [PLM] Baked contribution from high intensity HDRIs is not handled properly in linear color space
k0mbain
Jan 19, 2018 13:15
Present in 2017.1.2p3. It has almost 2 years. Duh!
LKWD_JamesD
May 02, 2017 09:26
Present in 5.4.5f1.
Is there any way to catch these?
Tinus
May 24, 2016 16:54
Just ran into this issue. We're trying to route all exceptions to GetSentry.com, a REST service but are having significant trouble finding the correct point to insert logging hooks. Capturing all Debug.Log callbacks can be done through multiple means, but this appears to be the only place to get exceptions.
Except, while the LogFormat callback of the ILogHandler interface is called, the LogException callback is completely dormant.
This is still an issue as of 5.3.5f1