Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2023.1.0a6
2023.2.0a1
2023.3.0a3
Issue ID
UUM-6059
Regression
No
[WebGL] "Uncaught TypeError: something is undefined" error freezes the player when thrown
How to reproduce:
1. Open the user-attached project (My project.zip)
2. Make sure that SampleScene is open
3. Build and Run the project for WebGL
4. In the browser player view press the button in the middle
5. Observe the error
6. Close the error window
7. Try pressing the button again
Expected result: the player is no longer interactable and is frozen
Actual result: the button can be pressed again
Reproducible with: 2019.4.40f1, 2020.3.36f1, 2021.3.5f1, 2022.1.6f1, 2022.2.0a17
Reproducible on: Windows 10, Ubuntu 20.04
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
- Input field does not update when selecting the same input field after previous input was canceled
- No warning thrown when modifying array size while editing multiple objects
- Root Motion Node option does not revert when changing the selection and clicking "Revert" in Inspector
- VFX Graph prefabs are not fully instanced when they are instantiated via a script
- All 2026-promoted builds incorrectly display outdated copyright year © 2025 instead of © 2026
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.
Resolution Note (2023.3.X):
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.