Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
Duplicate in 2019.4.X
Votes
29
Found in
2019.4
2020.2.1f1
2020.3
2021.1
2021.2
Issue ID
1323832
Regression
Yes
[WebGL] "SharedArrayBuffer will require cross-origin isolation as of M91" warning is thrown when launching Player on Chrome
How to reproduce:
1. Create a new project using the default 3D template
2. Make a WebGL build
3. Open the built Player on Chrome
4. In the browser, open the Developer Console (F12)
5. Inspect the logs
Expected result: "SharedArrayBuffer will require cross-origin isolation as of M91" warning shouldn't be thrown as SharedArrayBuffer is not used
Actual result: "SharedArrayBuffer will require cross-origin isolation as of M91" warning is thrown
Reproducible with: 2019.4.24f1, 2020.3.3f1, 2021.1.2f1, 2021.2.0a12
Not reproducible with: 2018.4.33f1
Comments (2)
-
fourDshopper
Aug 20, 2021 07:40
Kindly fix in LTS 2019 version as well. Thanks.
-
DerBernie
Apr 09, 2021 12:09
My expectation from Unity:
* get rid of SharedArrayBuffer usage (if possible) in a bugfix and/or
* update the docs accordingly (WebGL deployment) if changes are requiredThx!
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
- URP Cascaded Shadows do not have a falloff in Player when the Player is built not in Development Mode
- Grid in animation preview window is rendered on top of the object
- WebGPU Graphics.RenderPrimitives fails on MeshTopology.Quads with Validation errors when exceeding 64k vertices
- Task status is "WaitingForActivation" when awaiting a faulted task inside that task
- 0 is returned when any output from Split Node is input into the Lerp Node
Resolution Note (fix version 2021.2):
Fixed in Unity 2021.2.0a16
Resolution Note (fix version 2021.1):
Fixed in Unity 2021.1.7f1
Resolution Note (fix version 2020.3):
Fixed in Unity 2020.3.9f1