Search Issue Tracker
Fixed
Fixed in 2021.3.41f1, 2022.3.35f1, 6000.0.6f1, 7000.0.0a1
Votes
0
Found in
2021.3.38f1
2022.3.30f1
6000.0.3f1
7000.0.0a1
Issue ID
UUM-73104
Regression
No
[iOS] Memory leaks occur when UnityWebRequest.Get() is called
How to reproduce:
1. Download and open the attached project for iOS
2. In the Xcode toolbar, press "Product" > "Profile"
3. In the Profiler window, select the "Allocations" tool.
4. Switch the Allocations view mode to "Generations" and press the record button
5. On the iPhone, press the "Test" button
6. On the Allocations tool, press the Mark Generation button located at the bottom.
7. Repeat steps 5-6 several times
Expected outcome: No memory leaks occur
Actual outcome: Memory leaks occur every time UnityWebRequest.Get() is called. ( 32 Bytes )
Reproducible with: 2021.3.38f1, 2022.3.31f1, 2023.2.20f1, 6000.0.4f1
Reproduced on: iPhone 12 Pro (iOS 14.2.1), iPhone 13 Pro (iOS 16.6.1)
Note: Image showcasing actual results is attached (unitywebRequestequest_allocations.png )
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
- Dragging and dropping a system that contains event context to create nested VFX crashes the editor
- TextMeshPro UV2 custom data not rendering for off-screen text with RectMask2D in Unity 6
- Text overlap and is unreadable in Inspector > Terrain Paint Texture after creating new Terrain Layer
- Event "XRInputSubsystem.trackingOriginUpdated" triggers twice when recentering the view
- UITK TextField value is overwritten incorrectly by the converter result when Binding Mode is set to "To Source"
Resolution Note (fix version 6000.0.6f1):
Verified with 6000.0.6f1