Search Issue Tracker
Fixed
Fixed in 2020.3.39f1, 2021.3.10f1, 2022.1.15f1
Votes
0
Found in
2020.3.34f1
2021.3.3f1
2022.1.1f1
Issue ID
UUM-953
Regression
No
[Backport] UnityWebRequest interrupted before completion causes memory leak
Reproduction steps:
1. Open user-submitted project
2. Open the "TestScene" scene in the Assets folder
3. Open Profiler by navigating to Windows -> Analysis -> Profiler
4. Turn on Memory Profiler Module by navigating to Profiler Modules -> Memory
5. Enter Play Mode
6. Press Take Sample Playmode in the Profiler
7. Observe the Memory Used by Not saved -> Texture 2D
8. Wait for 5s and repeat steps 6 and 7
Expected result: The memory used by Not Saved -> Texture 2D didn't increase
Actual result: The memory used by Not Saved -> Texture 2D has increased
Reproducible with: 2019.4.36f1, 2020.3.30f1, 2021.2.13f1, 2022.1.0b9, 2022.2.0a5
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
- A vertical graphical artifact appears on Android Player when clearing Z & Stencil Buffer and running with OpenGLES3 Graphics API
- Player crashes when built with IL2CPP Scripting backend
- TextMeshPro package throws multiple Shader errors when importing TMP Essential Resources
- Package Manager search text field has no validation and leads to Editor freezes
- PlayerLoop.SetPlayerLoop() function is ignored when playing game in Player
Basamas
Nov 08, 2022 14:59
Might this fix be the cause of our webgl crashes introduced since 2021.3.10?
Our WebGL application now crashes at a point where textures are loaded via webrequests, and sometimes interupted before they get to finish.
The crashes started since 2021.3.10, and do no occur in 2021.3.9. This bugfix seems to be the only thing that is the plausible cause, because this is the only change related to unitywebrequests and textures