Search Issue Tracker
Active
Under Consideration for 1.21.X, 2.0.X
Votes
0
Found in [Package]
1.21.20
2.0.8
Issue ID
ADDR-3680
Regression
No
The Editor becomes unresponsive when using WaitForCompletion function while loading Addressable assets which are responsible for loading an additional scene
How to reproduce:
1. Open the “EmptyProject2022“ project
2. Open the “Window > Asset Management > Addressables > Groups“
3. Select Play Mode Script, and choose Use Existing Builds mode
4. Select “Build > New Build > Default Build Script”
5. Open the “Driver“ scene
6. Enter the Play Mode
7. Move the mouse around
Expected result: The Editor is responsive
Actual result: The Editor becomes unresponsive
Reproducible with: 1.21.19 (2022.3.25f1), 1.21.20 (2022.3.25f1, 2023.2.19f1, 6000.0.0b15), 2.0.8 (2023.2.19f1, 6000.0.0b15),
Could not test with: 1.21.19, 1.21.20 (2021.3.37f1) (Couldn’t resolve the Console exceptions)
Reproducible on: macOS 13.5.2 (Intel), Windows 10 Pro
Not reproducible on: No other environments tested
Note: Some asynchronous operation (coming from the {{Addressables.LoadAssetAsync<Object>}}()) is holding the WaitForCompletion function not finished and it is holding the Awake() function, thus holding the Editor unresponsive.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Profiler does not profile after building the Project with Autoconnect Profiler Option enabled
- Editor slows down when selecting a script with the [HideInInspector] attribute on arrays with dynamic values
- [XR] Custom Pass not working as intended with Single Pass Instanced when XR is initialized after runtime start
- NullReferenceException floods the Console when Previewing Probe Adjustments before Probe Volume Baking is finished, Prove Volume Baking hangs
- Managed Reserved Memory is adding up every time when a custom asset is uploaded into the scene
Add comment