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
- 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
Add comment