Search Issue Tracker
Fixed in 2019.2
Fixed in 2019.3
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
- LineRenderer points lists suffers from performance issues when list is large
- Shaders take a lot of memory at runtime even when only one variant is used
- Lego Microgame crashes the Linux Editor at "ScanFilter::Merge" when selecting a WebGL build location
- GameObject reference is null when creating it inside Reset() function and assigning Script as component
- GameObject/Prefab inspector preview is slow for complex hierarchies
Add comment