Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2019.3.0a3
2019.4
2019.4.19f1
2020.3
2021.1
2021.2
Issue ID
1315244
Regression
Yes
[iOS] Deadlock when continually sending UnityWebRequests and internet connection is disabled
Steps to reproduce:
0. Disable the internet connection in the device that's being tested
1. Open the "CrashTest (1).zip" project
2. Build the project for iOS
3. Deploy the project from Xcode
4. Pause program execution
5. Inspect the all the threads waiting for writeBody (+[UnityURLRequest writeBody:task:udata:])
Expected result: Threads don't stack up resulting in a deadlock due to no available space to write into
Actual result: Threads run out of space to write into and create a deadlock
Reproducible with: 2019.3.0a3, 2019.4.22f1, 2020.3.0f1, 2021.1.0b11, 2021.2.0a8
Not reproducible with: 2018.4.32f1, 2019.3.0a2
Devices tested on:
- iPad 9.7" 6th gen (14.4)
- iPad Air 2 (11.0.3)
- iPhone XR (13.4.1)
- iPhone 6 (12.4.8)
- iPhone 7 (12.3.1)
- iPhone 8 Plus (12.0)
- iPhone 12 Mini (14.1)
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
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
- [iOS] Multiple Xcode project instances created before opens up when performing Build and Run for iOS Platform
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a9
Resolution Note (fix version 2020.3):
Fixed in 2020.3.4f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.24f1