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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment