Search Issue Tracker
By Design
Votes
0
Found in
2021.3.27f1
2022.3.1f1
2023.1.0b20
2023.2.0a18
Issue ID
UUM-40050
Regression
No
Unity Web Requests failing when doing large quantity of requests
Reproduction steps:
1. Extract the attached zip file “ReproProject”
2. In the extracted folder open the “BundlesToCopy” folder and copy all the files and paste them into the "/Library/WebServer/Documents/" folder (on macOS)
3. Start the Apache server in Mac Terminal using the “sudo apachectl start” command
4. Open the “ReproProject” project in Unity
5. Open the “Assets/Scenes/SampleScene” Scene
6. Enter the Play mode
7. Wait for messages in the Console window
Expected result: Only “WebRequest OK from http://localhost//bundle_x” messages are printed to the Console
Actual result: Some requests timeout with the error “Curl error 28: Failed to connect to localhost port 80 after 25905 ms: Operation timed out”
Reproducible with: 2021.3.27f1, 2022.3.1f1, 2023.1.0b20, 2023.2.0a18
Reproducible on: macOS 13.3 (Intel)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
The issue lies in Apache server not able to handle a lot of request in short amount of time and it is not Unity fault. 1000 requests in one frame makes Apache server to reject or timeout requests. With better server setup this can be solved.