Search Issue Tracker
Fixed in 5.6.0
Votes
1
Found in
5.6.0b9
Issue ID
883484
Regression
Yes
[WebGL] [Chrome] Specific project doesn't work on Chrome with 'Module is not defined' error
To reproduce:
1) Open attached project
2) Open BasicSetup scene
3) Build and run on WebGL
4) Try to run on Chrome
It fails with this error: http://puu.sh/udeM8/2f00695476.png
This is the console output: http://puu.sh/udeVK/1ff8716bb1.png http://puu.sh/udeUV/86a21661ec.png
Only happens in Chrome 56.0.2924.76 (64-bit).
Doesn't happen in Chrome Incognito mode or Firefox
Reproduced in 5.6.0b1(there instead an "Uncaught Webassembly support is not available on this browser" is thrown), 5.6.0b6, 5.6.0b9
Not reproduced in 5.5.2f1
As Stefan asked, will note that WebAssembly option in Editor is disabled and both webassembly flags in chrome are set to "Default"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment