Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
2019.3
2020.1
Issue ID
1186265
Regression
No
Splash screen resources are not unloaded from memory
How to reproduce:
1. Open the attached project (1186265test.zip)
2. Build and run the project (make sure Development Build is enabled)
3. After the splash screen in the Player ends, go into the Editor -> Window -> Analysis -> Memory Profiler
4. Switch from 'Editor' to the Player that is currently running and take a snapshot
5. Open the snapshot and sort the memory table by 'OwnedSize'
6. Notice that 'splash_logo' is high on the list (around ~150 KB owned size)
Expected result: Splash screen resources are not present in memory
Actual result: Splash screen resources are kept in memory
Reproducible with: 2018.4.17f1, 2019.3.1f1, 2020.1.0a23
Could not test with earlier versions due to Memory Profiler either throwing errors or crashing Unity altogether
Note:
- Seems to be a regression from https://fogbugz.unity3d.com/f/cases/960554, but the bug was present where I could test with this method
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
- Crash on block_locate_free when rendering a specific scene
- A submenu disappears on MacOS when the MenuItem method argument "isVariableFunction" is set to "false" and priority argument is set to "-1"
- The Sprite Library Editor window has an incorrect order of Sprites when the Sprites are reordered and the order saved
- Tilemap Tiles do not get lit up unless the Light Range is greater than the distance between the position of the Tile before the transformation and the Light Source when the Tile is transformed with Tilemap.SetTransformMatrix method
- The Editor and "Reloading Domain" windows are frozen when entering Play Mode
Resolution Note (fix version 2020.2):
Fixed in version 2020.2.0a12
Resolution Note (fix version 2020.1):
Fixed in version 2020.1.0b14
Resolution Note (fix version 2019.4):
Fixed in version 2019.4.3f1
Resolution Note (fix version 2018.4):
Fixed in version 2018.4.27f1