Search Issue Tracker
Won't Fix
Votes
2
Found in
2022.1.0a16
2022.2.0a11
Issue ID
UUM-2870
Regression
No
[Accelerator] Editor freezes during asynchronous upload "On demand scheduler transport error"
Reproduction steps:
1. Pull the GitHub repo provided in the initial report
2. Open the Unity project (it will be connected to an Accelerator cache server)
3. In the Project window click the second mouse button to bring out the context menu
4. Go Create -> Asset Generator -> Extreme (500MB)
5. A .txt Asset will be created and the upload to the server will start in the background
Expected result: The asset is created and is being uploaded to the cache server in the background. You can use the editor for other things.
Actual result: The asset is created and is being uploaded to the cache server in the background. During the upload the editor freezes completely, after the upload completes "On demand scheduler transport error" is thrown
6. If the issue did not reproduce, reimport the created asset until the issue reproduces
Reproducible with: 2022.1.0a1, 2022.1.0a5
Could not test with 2021.2.0a21 or earlier because the feature was not yet implemented
Please check Vitaly's comment - might be the same issue or new one.
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.