Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.2.0f3
Issue ID
971531
Regression
No
Memory leak caused when a static flag is set to 'lightmap static' on an imported model game object
Steps to reproduce:
1. Open user attached project
2. Open the scene "leaks.unity" in Assets->Scenes
3. Open Task Manager in Windows, see memory increases about 500 MB per second
Expected result: enabling 'lightmap static' of an imported model game object should not cause a memory leak
Reproduced in: 2018.1.0a5, 2017.3.b10, 2017.2.0f3, 2017.1.2p3, 5.6.4p3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment