Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2022.1.0a12
2022.1.0a13
Issue ID
1377289
Regression
Yes
[WebGL] RuntimeError: memory access out of bounds when Building and Running Build
Reproduction steps:
1. Open the user's attached project
2. Set ILC2PP Code Generation to Faster (smaller) builds
3. Build And Run the Project
Expected result: Build runs
Actual result: Build shows "RuntimeError: memory access out of bounds"
Reproducible with: 2022.1.0a12, 2022.1.0a13
Not reproducible with: 2020.3.25f1, 2021.2.0f1, 2022.1.0a11, 2022.1.0a14, 2022.1.0b2
Could not test with: 2019.4.34f1 (error CS0305: Using the generic type 'Progress<T>' requires 1 type arguments)
Note: the error is inconsistent, on some versions you need to set ILC2PP Code Generation to Faster (smaller) builds, on some not
-
theylovegames
Apr 24, 2022 23:47
The issue reproduces in 2021.3.1f1 and 2022.2.0a10 -
https://answers.unity.com/questions/1798594/webgl-runtimeerror-memory-access-out-of-bounds-2.html
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
- 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
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a14