Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2021.2.0b15
2022.1
Issue ID
1372741
Regression
No
[UWP] Visual Studio output throws exception when the Camera GameObject has 2 post processors in UWP build
Reproduction steps:
1. Open project "UWPDoublePostProcessBug.zip"
2. Open Scene "SampleScene"
3. Open Build Settings window from File > Build Settings
4. Switch Platform to Universal Windows Platform and build the project
5. Open the solution of the project then launch the application
6. Observe Output window from Debug in Visual Studio
Expected result: No exceptions are thrown
Actual result: Exceptions are thrown
Reproducible with: 2019.4.32f1, 2020.3.23f1, 2021.1.28f1, 2021.2.3f1, 2022.1.0a15
Error: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Resolution Note:
This error is internally thrown and handled by the D3D11 debug layer, which is only enabled in debug builds. This happens because the debug layer tries to validate a texture we're discarding by rendering to it but the texture isn't renderable and it thus throws an exception (which it then catches itself). This is not a flaw in Unity and it does not affect anything. It also doesn't happen in Release and Master build configurations.