Search Issue Tracker
Fixed in 5.5.3
Votes
5
Found in
5.4.0p1
Issue ID
827299
Regression
Yes
Loading.LockPersistentManager object lock impacts performance during AssetBundle.LoadAssetAsync operation
Loading.LockPersistentManager object lock impacts performance during AssetBundle.LoadAssetAsync operation.
Developers suggested deferring of the lookup or rwlock might improve AssetBundle.LoadAssetAsync behavior or it should be just fixed perhaps by deferring AssetBundleLoadAssetOperation::PreparePreloadAssets to preloading thread.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Variant Collection Asset UI is hard to read when multiple Shaders and keywords are added
- Resetting Quality Levels in Project Settings adds new Quality Levels instead of restoring default ones
- UI builder uxml files retain reference to non-existing assembly definition file when a assembly definition file is deleted
- Animator Entry and Base Layer Transitions links to the documentation aren’t working
- Caret doesn't appear when clicking the Input Field on secondary monitor
Add comment