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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.