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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Add comment