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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Package signature validation unexpectedly return an invalid signature status if the validation check is done after the code signing certificate validaty range has passed
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
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?