Search Issue Tracker
By Design
Votes
2
Found in [Package]
1.21.20
2.1.0
Issue ID
ADDR-3664
Regression
Yes
Initialize Synchronously locks the player
*Steps to reproduce:*
1. Open attached project
2. Create a windows player build.
3. Start the build. The game will not start.
4. Go into the editor and disable Localization Settings / Initialize Synchronously.
5. Create another build. Notice this one starts up.
Note: Initialize Synchronously just calls WaitForCompletion on the LocalizationInitialization operation.
*Reproducible with versions:* 1.5.0-pre.6
*Not reproducible with versions:* 1.5.0-pre.5
*Can’t test with versions:*
*Tested on (OS):* Windows
*Notes:*
*
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
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
Resolution Note:
When we start loading a file we take a lock in the PersistentManager to ensure the same file or its dependencies don't get loaded multiple times and create duplicate objects.
This impose some limitation on the synchronous asset loading: we can't synchronously load an asset in a callback triggered by loading of another asset.
In this case we load the managers config file which creates LocalizationManager on the main thread and them the LocalizationManager tries to load an asset bundle synchronously from the OnEnable.