Search Issue Tracker
By Design
By Design in 2.1.X
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:
Comments (1)
-
Peter77
May 20, 2024 07:56
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.
Resolution Note (2.1.X):
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.