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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.