Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.5.0f3
Issue ID
884636
Regression
Yes
Cloning and deleting the same terrain many times, causes memory leak
To reproduce:
1. Open attached repro project
2. Open 'Test' scene
3. Open activity monitor
4. Clone '10 terrains' game object 5-7 times
5. Notice that memory usage increased as expected;
6. Delete all clones
Expected: memory usage will be the same as before cloning '10 terrains' game object
Actual: memory usage is the same as with 5-7 clones
or
1. Download project from here: https://oc.unity3d.com/index.php/s/o3J3MjDXJRjhn2t
2. Open 'TestScene';
3. Open Profiler (ctrl/cmd + 7) and 'Memory' tab;
4. Launch the scene;
5. Press X multiple times;
6. Observe that 'Used total' field is increasing. Also memory consumption is Activity Monitor or Task Manager is steadily increasing.
Regression between: 5.4.3f1 -> 5.4.3p2
5.5.0f1 -> 5.5.0f2
5.6.0a3 -> 5.6.0a5
Reproduced on: 5.4.4p3, 5.5.2f1, 5.6.0b10,
Not reproduced on: 5.4.3f1, 5.5.0a6, f1, 2017.1.0a1
Tested on: OSX 10.12.2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Rendering Debugger] Shortcut in documentation to open window doesn't work
- The "Compress Tilemap Borders" function is not working when used via the Context Menu or through Script
- HDRP Sorting Priority not working when Render Pass is locked on a parent material
- [XR] Camera view rendered by the RenderTexture is not updated at runtime when XR is enabled
- Lens Flare occlusion is slightly delayed when Anti-aliasing is set to TAA
Add comment