Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.3f1
Issue ID
942153
Regression
Yes
Crash on RenderImageFilters if trying to render with Camera that is already rendering
How to reproduce:
1. Open "CameraCrash.zip" project
2. Open the "scene" scene
3. Enter Play mode
4. Exit Play mode
Actual result: Unity crashes.
Reproducible with: 5.6.0p4, 5.6.3f1, 2017.1.0p4, 2017.2.0b8, 2017.3.0a5.
Regression introduced in: 5.6.0p4.
Not reproducible with: 5.6.0p3, 5.5.4p2.
Note: with 5.6.0p3 and previous versions Unity doesn't crash, but errors "Assertion failed on expression: 'm_DepthTexture == NULL && m_DepthNormalsTexture == NULL'" and "Recursive initialization of the renderloop context. This will leak a lot of memory." appears.
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
Recursive camera rendering isn't supported and is not a behavior we intend to support.
It wasn't really supported before either but there was a hack in-place to somewhat alleviate the problem. As far as I can remember, this hack caused a lot of side-effects and removing it fixed a lot of side-issues in the camera rendering logic.