Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2018.4
2019.2
2019.2.6f1
2019.3
2020.1
Issue ID
1201307
Regression
No
Memory is leaking when Standalone Player window is being resized without focusing it
How to reproduce:
1. Open the attached 'project-1201307.zip' project
2. Build and run the standalone
3. Open Windows Task Manager and focus it
4. Keep resizing the player without focusing it
5. Observe the Memory usage while resizing the standalone
Expected result: Memory usage does not increase
Actual result: Memory usage increases rapidly (memory is leaking)
Reproducible with: 2017.4.35f1, 2018.4.13f1, 2019.2.14f1, 2019.3.0f1, 2020.1.0a15
Additional note: releasing the mouse after resizing returns the memory usage to normal
Required build settings:
- 'Resizable Window' enabled
- 'Run In Background' disabled
- 'Fullscreen Mode' set to 'Windowed'
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2020.1.X):
Since memory comes back at the end of resize the user impact is minimal