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
- 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 (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.