Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.31f1
Issue ID
UUM-53865
Regression
No
[WebGL] "RuntimeError: Out of bounds memory access" error appears when pressing the button created with UI Toolkit in WebGL on iOS devices
How to reproduce:
1. Build the user’s attached “UIButtonWebGLTest.zip” project for WebGL
2. Open the project on an iOS device
3. Press the play button
4. Press the “Start” button and observe the result
Expected result: No errors
Actual result: "RuntimeError: Out of bounds memory access” error appears
Reproducible with: 2021.3.31f1
Not reproducible with: 2022.1.11f1, 2022.1.24f1, 2022.3.11f1, 2023.1.17f1, 2023.2.0b14, 2023.3.0a10
Could not test with: 2022.1.10f1 (button is not visible)
Reproduced on:
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
Not reproducible on: Android, Windows, macOS
Note: reproducible with Safari and Chrome browsers
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
- VFX Graph font size change does not adjust Sticky Note size when smaller font size is selected
- Rendering Debugger has a “Go to Section” burger button even when the section is already opened and does nothing when pressed
- SIGSEGV error when adding EditorApplication.delayCall callback declared in complex generic type and exiting Unity in `Performanc
- Resize cursor does not appear while approaching window edge from inside the player window when using Input System as the Input Handler
- IMGUI Debugger Instructions are flickering when the Inspected View is set to Scene and mouse cursor is moved over the Scene View
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.