Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2019.3.X
Votes
2
Found in
2019.2.0a6
2019.2.13f1
Issue ID
1199895
Regression
Yes
Native Graphics Jobs Memory Leak
A memory leak introduced in 2019.2 (changeset 58248f4d2234) causes an eventual crash when running with Native Graphics Jobs.
Reproduction Steps:
1. Clone Viking Village https://ono.unity3d.com/unity-extra/unity-assets/BenchRenderVikingVillageStatic
2. Open for PS4 or PC+Vulkan
3. Ensure Native Graphics Jobs are enabled
4. Build & Run
5a. After some time (under an hour) a crash will occur
5b. Attach a memory analyser, and observe the memory leak
Reproducible in versions 2019.2.0a6 and newer.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment