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
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
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
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?