Search Issue Tracker
Fixed in 2017.4.X
Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X
Votes
0
Found in
2017.3.1p1
Issue ID
1005779
Regression
No
[Procedural Material]Performing initial generation of multiple substances at once leaks significant amounts of memory
Steps to reproduce:
1. Open attached project "SubstanceLeaking.zip"
2. Open "Playground" scene
3. Open profiler and observe the memory tab or open Task manager and watch Unity's used memory
4. Select "Tester" gameobject and select "Initial Generation Concurrent" in the "Test to run" field
5. Observe memory pooling up and not being cleared even when play mode is stopped.
Expected: Memory should be cleaned up after Gameobject/texture is destroyed.
Actual: In a very short time period memory will pool up and not get cleaned up until you shut down the editor
Reproduced on: 5.6.5p2, 2017.1.3p1, 2017.2.2f1, 2017.3.1p2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment