Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.1f1
Issue ID
912235
Regression
No
Huge memory leak while previewing LOD bias in Scene View
To reproduce:
1. In a new project, create a cube
2. Add LOD Group component to the cube
3. Open Scene view
4, Drag camera icon in the LOD Group component in the Inspector
5. Observe memory usage of the Editor in Task Manager
Expected: using LOD Group does make Unity use 5 GB of memory
Actual: Unity uses a few GB of memory when using LOD Group component
Reproduced in 5.6.1f1
Did not reproduce in 2017.1.0b1, 2017.1.0b6
Fixed in 2017.1.0b1
Comments (2)
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
- “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
JustMoof
Jul 19, 2017 15:17
I'm getting this issue in 2017.2.0b3. Picture showing the extreme memory usage: http://i.imgur.com/kNQXIXl.png . I also tested this using the steps above in a new project and encountered the same problem.
jwilliamsen
Jun 19, 2017 21:49
So, is this not going to get fixed in 5.6.X? This is the THIRD huge memory leak that I've run into and I'm seeing that on all of them (on issuetracker) so far it appears that Unity is just abandoning 5.6 because they're supposedly "fixed" in the 2017 beta? Is this correct?