Search Issue Tracker
By Design
Votes
0
Found in
2019.1.12f1
2019.2
2019.3
2020.1
Issue ID
1192390
Regression
No
Profilers shows that GameObject still uses Memory when the GameObject is unloaded
Steps to reproduce:
1. Open the attached project "Case_1192390"
2. Open "SampleScene"
3. Enter Play mode
4. Press GenerateButton on GUI. a prefab with the image component will be
instantiated.
5. Press Destroy Button on GUI.
6. Press Unload Button on GUI.
7. Open Profiler with Deep Profiling
8. Check Memory-> Gather object references-> Assets -> Texture2D
Expected results: Unloaded GameObject should not use any Memory
Actual results: Profiler shows that Unloaded GameObject still uses Memory
Reproducible with: 2019.2.10f1, 2019.3.0b7, 2020.1.0a9
Note: 2019.2.0a2 and lower brake the UI elements and the scripts in the project
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Closing as By-Design as instructed by Martin Schmitz, since the issue does not reproduce with a build