Search Issue Tracker
By Design
Votes
1
Found in
2019.4
2019.4.29f1
2020.1
Issue ID
1363710
Regression
No
[WebGL] "memory access out of bounds" error is thrown when running a WebGL build on Chrome via a file:// path
"RuntimeError: memory access out of bounds" error is thrown when running a WebGL build on Chrome via a file:// path using --allow-file-access-from-files
How to reproduce:
1. Close any active instances of Google Chrome
2. Open a Terminal window
3. Type "open -a "Google Chrome" --args --allow-file-access-from-files" and press Enter
4. In the attached build "Build 2019.4.33f1", open "index.html" with Google Chrome
Expected result: The build displays the "test.png" image
Actual result: The build shows a blank screen
Reproducible with: 2019.4.33f1, 2020.1.0a6
Could not test with: 2020.1.0a7, 2020.3.23f1, 2021.2.3f1, 2022.1.0a15 (Error: Ensure CORS requests are made on supported schemes)
Notes:
1. Reproduced on Chrome Version 96.0.4664.55
2. The build works as expected when running from a local server
3. The error is not reproducible on any Unity version and works as expected with Firefox
Errors in Chrome's Console:
UnityLoader.js:1150 exception thrown: RuntimeError: memory access out of bounds,RuntimeError: memory access out of bounds
Invoking error handler due to
Uncaught RuntimeError: memory access out of bounds
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
- The tag adder functionality does not work if a space is entered instead of a name
- Errors thrown in the Console when configuring In-App Purchases package
- Longer Scaler Profile names go out of the"Scaler Profilers" section
- AI Navigation window UI elements overlap when the AI Navigation window is docked and resized
- Editor freezes after some time when using NavMeshQuery::Raycast
Resolution Note (2022.2.X):
Thank you for opening the bug. However, the Unity WebGL build target is designed for usage via a web server. We are unable to provide workarounds for browser limitations when accessing content locally via a file:// url.