Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
2
Found in
2022.2.0a11
2023.2.0a1
Issue ID
UUM-731
Regression
No
RuntimeError is thrown on WebGL when running empty 3D URP template project
How to reproduce:
1. Create a new empty project from the 3D (URP) blank template (without Sample Scene)
2. Build and run the project for WebGL
3. Observe the Player in the browser
Expected result: the Player runs
Actual result: 'RuntimeError: memory access out of bounds' error is thrown
Reproducible with: 2021.3.1f1, 2022.1.0f1, 2022.2.0a11
Could not test with: 2019.4.38f1 (.../net471/il2cpp.exe did not run properly\!), 2020.3.33f1 (Exception: Unity.IL2CPP.Building.BuilderFailedException <...> error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory)
Notes:
1. Reproducible on Linux
2. Not reproducible on MacOS
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
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
Resolution Note:
Validated that a new project using the 3D (URP) blank template will successfully build and run in the following environment when targeting WebGL:
Editor: 2021.3.23f1
Ubuntu: 18.04.6
If this issue arises in a current or future LTS version please let us know.
Resolution Note (2023.2.X):
Validated that a new project using the 3D (URP) blank template will successfully build and run in the following environment when targeting WebGL:
Editor: 2021.3.23f1
Ubuntu: 18.04.6
If this issue arises in a current or future LTS version please let us know.