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
- Crash on RenderBufferManager::Textures::GetTempBuffer when rendering a specific scene
- The Inspector header is incorrectly displayed when scripts are recompiled while a Scriptable Object instance is selected
- NullReferenceException is thrown when overriding the UxmlObjectReferences in template instances
- Shaders created with Shader Graph generate a large amount of shader variants and cause slow build times when using a baked lightmap in BIRP
- Shader Graph Matrix property produces random output values when SRP Batcher is enabled
Add comment