Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
12.1.x
13.1.6
14.0.2
Issue ID
SGB-8
Regression
Yes
[HDRP][ShaderGraph] Memory leak when opening a Shader Graph window
How to reproduce:
1. Open the user-submitted project
2. Open the scene "Copy of SK_TestScene" (Assets/UI_Branch/Scenes/Copy of SK_TestScene.unity)
3. In the Project window, open the Shader Graph "BigMap Shader" (Assets/UI_Branch/Materials/BigMap Shader.shadergraph)
4. Inspect the Console window (Window > General > Console)
Expected result: No warnings are seen in the Console
Actual result: Warnings are spammed in the Console
Reproducible with: 12.1.0 (2021.2.1f1), 12.1.5 (2021.2.14f1), 13.1.6 (2022.1.0b10), 14.0.0 (2022.2.0a6)
Not reproducible with: 7.7.1 (2019.4.36f1), 10.8.1 (2020.3.30f1), 12.1.0 (2021.2.0f1)
Notes:
1. The Editor freezes after a while
2. The project may need to be launched twice to reproduce the issue
Full warnings:
Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak
Internal: deleting an allocation that is older than its permitted lifetime of 4 frames (age = 5)
Comments (1)
-
ashtorak
Jun 03, 2022 09:52
Any news on this?
I have the same issue on 2022.1.0b13
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
- ScrollView speed is slower when entering Play mode
- UI Builder elements disappear and "Semantic - Unknown template name" error appears when changes to "Template" parameter are saved
- Renderers outside Light Probe hull use incorrect Ambient Probe values when "Renderer Light Probe Selection" is set to "Use Ambient Probe" and "Light Probes" on Mesh is set to "Blend Probes"
- ArgumentNullException error occurs when selecting a Camera in the Hierarchy with the Scene view open
- Clicking 'Open Editor Log' through the Console fails to open redirected Logs when relative Log files exist outside of the Project root
Resolution Note:
Due to the age of the issue and the difficulty to reproduce this, we aren't expecting to address the problem in the near-term as a bugfix.