Search Issue Tracker
Fixed in 2019.3.X
Votes
9
Found in
2019.3
2019.3.0f3
2020.1
Issue ID
1205918
Regression
Yes
[HDRP] HDRI and Physically Based sky cause memory leaks when the sun is updated every frame
How to reproduce:
1. Open the attached "SkyRenderMemLeak" project
2. Open the "TestMemoryLeak" scene
3. Open the Profiler window
4. Enter Play mode
5. In the Hierarchy, select the SimWorld GameObject
6. In the Inspector, enable the "Update_sun" property and inspect the Profiler
Expected results: There is no significant decrease in performance or increase memory usage
Actual results: Performance decreases and memory usage increases significantly
Reproducible with: 2019.3.0f1, 2019.3.0f4 (HDRP 7.1.6), 2020.1.0a17 (HDRP 7.1.7)
Not reproducible with: 2019.3.0f1 (HDRP 7.1.5)
Note: With "Update_sun" enabled, a memory snapshot shows many "InScatteredRadianceTable" and "SkyboxCubemap" objects under Not Saved > RenderTexture
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
SHKrAtWork
Apr 24, 2020 20:10
This issue is causing huge problem in our release too, this seems to be critical now. Is this fixed yet?
DeathRace26
Apr 19, 2020 18:11
This is not fixed. I'm still experiencing memory leaks in 2019.10, HDRP 7.3.1.
Lynxed
Apr 02, 2020 18:21
This is NOT fixed in 2019.3.1f7 HDRP 7.1.8
It starts happening if you move your physical lighting every frame (day\night cycle) and open one more editor viewport or select material\camera in inspector .
OrthrusOliver
Mar 10, 2020 03:32
Still failing in 2019.3.2f1 HDRP 7.1.8
It makes our game Unplayable and the Editor unusable. We are due to release in the very near future, but cannot with this Bug.
We cannot upgrade to 7.2.0 where it is supposedly fixed (although not seeing any evidence of that in our test upgrades).
We need a fix or a workaround ASAP because right now we're supposedly using 15GB of VRAM for no real reason.
paragraph7
Feb 28, 2020 13:38
Still happening in 2019.3.0f6 HDRP, when moving directional light every frame.
Albarnie
Feb 12, 2020 03:03
Not fixed in 2019.3.0f6. using 41GB of ram from InScatteredRadianceTable each 32mb in size.
Bastienre4
Feb 07, 2020 12:13
This is a huge problem for us. It also compromises our next milestone.
crysicle
Feb 06, 2020 16:00
Need to RR the editor every 30-60 mins because of this. According to the profiler they end up taking 12GB+ and everything that has to do with RenderTextures starts misbehaving. Getting a lot of errors:
D3D11: Failed to create render texture primary RTV (error 0x887c0003)
D3D11: Failed to create render texture secondary RTV (error 0x887c0003)
Momo_Manbavaran
Feb 06, 2020 00:48
Also experiencing this in 2019.3.0F6
alia_0
Feb 04, 2020 18:17
This still fails on Unity 2019.3.0f6 and the following in the manifest file:
"com.unity.postprocessing": "2.3.0",
"com.unity.render-pipelines.high-definition": "7.1.8",
"com.unity.scriptablebuildpipeline": "1.6.3-preview",