Search Issue Tracker
Fixed in 7.1.8
Votes
0
Found in [Package]
7.1.7
Issue ID
1210688
Regression
Yes
[Shadergraph] Memory leak after repeatedly closing and opening complex shadergraph
Reproduces with SRP 7.1.7 in 2019.3. Does not reproduce in 2019.2 (SRP 6.9.2).
Reproduces in Version: 2020.1.0a18.2166 with SRP master commit 8823d0532c
Reproduces on Release/2019.3 branch of SRP, commit 4ebdde3ed6
Repro steps:
1. Use a project with Universal RP (do not have to have pipeline asset installed in graphics settings for bug to reproduce)
2. Download attached shadergraph and bring it into project
3. Open task manager to track the memory Unity is using
4. Open the shadergraph, note that the shadergraph's performance is good
5. Close and reopen the shadergraph 10 times
Expected result: no memory leak
Actual result: Unity is now taking up around a gig more memory
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
Add comment