Search Issue Tracker
Fixed in 1.3.3
Votes
2
Found in [Package]
1.1.7
Issue ID
1176085
Regression
Yes
[Addressables] [WebGL] Exceptions are thrown when using Addressables.LoadSceneAsync() after webpage is reloaded
How to reproduce:
1. Open the attached project ("case_1176085-LoadTest.zip"), setting the platform to WebGL
2. Build Player Content
3. Make a WebGL build and run it
4. Use the "Load scene1", "Load scene2" and "Load prefab" buttons in the build
5. Notice that there are no errors in the developer's console
6. Refresh the page and click the buttons again
7. Notice the "Exception: Attempting to use an invalid operation handle" exceptions in the developer's console
Expected results: No exceptions are thrown, scenes get loaded the same way as before the refresh
Actual results: Exceptions are thrown
Reproducible with: 2019.3.0a12, 2019.2.1f1, 2019.3.0a12
Not reproducible with: 2018.4.6f1, 2019.1.14f1, 2019.2.0a11
Couldn't test with 2017.4 as it does not support the Addressables package
Reproducible with package versions: 0.8.6, 1.1.7
Tested with: Chrome (Version 76.0.3809.100 (Official Build) (64-bit)), Firefox (68.0.1 (64-bit))
Comments (1)
-
jjensch_
Sep 25, 2019 13:33
I could reproduce this with Chrome 77.0.3865.90 on Win10 x64 w/ Unity 2019.2.2f1 and Addressables 1.2.4.
I also found the refresh in chrome to work again after deleting the idbfs IndexedDB manually (works only once, since it recreates the idbfs database)
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Resolution Note (fix version 1.3.3):
This particular exception resolution has been verified in 1.3.3.