Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.1.0a1
2023.2.0a1
Issue ID
UUM-5525
Regression
No
iOS player freezes at semaphore_wait_trap when loading ~60000 AssetBundles using AssetBundle.LoadFromFile
How to reproduce:
1. Open the attached project ("LoadManyAssetTest.zip")
2. Build And Run on an iOS device
3. Wait until the counter stops at slightly under 60000
4. In Xcode, pause the application (ctrl + command + Y)
Expected result: The main thread does not freeze at "semaphore_wait_trap", AssetBundles continue to be loaded
Actual result: The main thread freezes at "semaphore_wait_trap", AssetBundles are no longer being loaded
Reproducible with: 2020.3.36f1, 2021.3.4f1, 2022.1.5f1, 2022.2.0a17
Could not test with: 2019.4.40f1 (AssetBundles were built with a newer version of Unity)
Reproducible on:
iPhone 13 mini (iOS 15)
iPad 6th gen (iOS 14.4.2)
Not reproducible on:
Editor
Note:
- May also be reproducible on Android (user-provided information)
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
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.