Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
Issue ID
1201213
Regression
Yes
[Windows][Video] Graphics memory leak in hardware-accelerated video decoding
This issue has no description.
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 (fix version 2020.1):
Now avoiding to share the same texture multiple times between the video-specific D3D11 device and the main D3D11/D3D11 Unity graphics device. Sharing textures between D3Dx devices creates a new object every time and unnecessarily reserves additional GPU address space.
Resolution Note (fix version 2019.3):
Avoid redundant sharing between video-specific D3D11 device and main D3D11/D3D12 graphics device.