Search Issue Tracker
Duplicate
Votes
0
Found in
2019.4
2019.4.29f1
2020.2
Issue ID
1356413
Regression
No
VRAM Leak when using RendererExtensions.updateGIMaterials()
How to reproduce:
1. Open users’ attached “vramtest.zip” project
2. Open Scene “SampleScene”
3. Open the Profiler window (Window -> Analysis -> Profiler)
4. Change the Profiler Modules so that only the ‘Rendering' Module is displayed
5. In the Hierarchy select GameObject “Cube” and in the Inspector enable the “Updategimaterials” script
6. Enter the Play Mode and observe RenderTextures memory usage in the Profiler
Expected results: RenderTextures memory stays constant
Actual results: RenderTextures memory keeps constantly increasing
Reproducible with: 2019.4.29f1, 2020.2.0a2
Not reproducible with: 2019.4.30f1, 2020.2.0a3, 2020.3.16f1, 2021.1.16f1, 2021.2.0b7, 2022.1.0a5
Notes:
- To observe expected results repeat steps 5-6 with the “Updategimaterials” script disabled.
-
Resolution Note (2019.4.X):
Fixed in 2019.4.30f1, 2020.2.0a3, and above
-
MerlinVR
Aug 25, 2021 18:11
Please backport this fix to 2019.4 LTS. As others have said, this is a commonly used feature in VRChat. And looking at VRChat's release schedule and the number of breaking changes to VR in 2020; due to this bug it is unlikely UGC will be able to use realtime GI for at least a year, if not more.
-
davidweil45
Aug 25, 2021 18:10
This fix should definitely be backported to LTS versions.
-
WACOMalt
Aug 25, 2021 03:10
This needs to be fixed in older LTS versions of unity as well! Present in 2019.4.29f1.
-
OwlBoy-
Aug 24, 2021 18:57
Please backport this fix to Unity 2019 LTS for VRChat users. It has a large impact there.
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
- 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
This is a duplicate of issue #1206727