Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2019.3.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.2.0f1
2019.3.0a1
2020.1.0a1
Issue ID
1177888
Regression
No
Memory leak when sending UnityWebRequests
How to reproduce:
1. Open the "WebRequest_Leak.zip" project
2. Open the "SampleScene.unity" scene
3. Enter Play Mode
4. Press the "Button" button
5. Check Unity's memory usage
Actual result: Unity app memory usage is slowly rising. (Screenshot attached)
Expected result: Unity app memory usage is not rising.
Reproducible with: 2020.1.0a1, 2019.3.0a12, 2019.2.2f1, 2018.4.7f1, 2017.4.32f1.
Devices reproducible with:
- VLNQA00272, Samsung Galaxy S10+ (SM-G975U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
- iPhone 7 (iOS 10.2)
Notes:
- Reproducible on iOS, Android and Editor.
- Not reproducible on Mac Standalone.
- It's easier to notice the leak on iOS.
----------------------------
Fixed in 2020.1.0a6, 2019.3.0b5, 2019.2.8f1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment