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
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
- The Hub freezes indefinitely when copy/pasting a lot of characters in the “Set project display name” Hub window since it has no character limit
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.