Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.3.0a5
2018.3.12f1
Issue ID
1145492
Regression
Yes
Memory leak when using TextAsset.bytes property
Reproduction steps:
1. Open the attached project inside of "_test_proj_memory_leak.zip"
2. Make sure Profiler with the Memory Tab is open
3. Open and Play the "SampleScene"
4. Press "F1" and then tap "F2" a few times
Expected result: Memory profiler shows no difference in total memory after F2 taps
Actual result: Memory profiler shows a memory leak after F2 tapping
Reproduces on: 2018.3.0a5, 2018.3.13f1
Does not reproduce on 2017.4.25f1, 2018.3.0a4, 2019.1.0f2, 2019.2.0a12
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
Add comment