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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment