Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0a5
2019.1.5f1
2019.2.0a1
2019.3.0a1
Issue ID
1160054
Regression
Yes
When using the Button component, Texture2D can't be unloaded after switching the Scene and/or using Resources.UnloadUnusedAssets
How to reproduce:
1. Open the user's project
2. Open the scene "TestA"
~it has a script which loads "TestB" scene when pressing Space~
3. Play
4. Open the Memory Profiler, Detailed, Take Sample Editor
5. Inspect Assets > Texture2D, it clearly has some sprites
6. Return to Game Window and press Space (it loads SceneB)
7. Take Sample Editor again
8. Inspect Assets > Texture2D, also has sprites, even though there are none in the scene
Expected result: Assets can be unloaded after switching the scene and Resources.UnloadUnusedAssets();
Actual result: Texture2D assets cannot be unloaded
Reproducible with - 2019.1.0a5, 2019.1.6f1, 2019.2.0b5, 2019.3.0a5
Not reproducible with - 2017.4.28f1, 2018.4.2f1, 2019.1.0a4 (some assets can be unloaded)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
- [Android] Virtual device crashes with "Scudo ERROR: invalid chunk state when deallocating address" error in Firebase Test Lab when Optimized Frame Pacing is enabled
- Particle System does not resume when its Culling Mode is set to "Pause" or "Pause and Catch-up," and particle position simulate in world space
- "Custom Render Queue" field cannot be set above "2000" when changing it in the Inspector window using Debug mode
Add comment