Search Issue Tracker
Not Reproducible
Not Reproducible in 2023.2.X
Votes
4
Found in
2021.3.27f1
2022.3.2f1
2023.1.0f1
2023.2.0a19
Issue ID
UUM-40053
Regression
No
WebGL build has low performance when running in Chrome on macOS
Reproduction steps:
1. Open the “ZIPPEDPROJECT” attached project
2. In the Menu bar click on File > Build Settings
3. Change Platform to WebGL
4. Click on “Unity Support” in the Menu bar
5. Press “Build & Run Player”
6. Copy the build URL from your default browser to Firefox, Chrome and Safari
7. Observe FPS count in the browsers
Expected result: Build on Chrome runs smoothly with 60fps (has a similar performance compared to Firefox and Safari)
Actual result: Build on Chrome is laggy with ~20 fps (lower performance compared to Firefox and Safari)
Reproducible with: 2021.3.27f1, 2022.3.2f1, 2023.1.0f1, 2023.2.0a19
Reproducible on: macOS Ventura 13.2.1 (M1 Max)
Not reproducible on: Windows 10
Comments (2)
-
UAS
Aug 13, 2023 03:44
UnityDevs Fix this asap,
all chromium browser for macOS (probably silicons) got slow WebGL buildsall fine, no problem for FireFox and Safari. Issue only from Chromium, Google Chrome - brave browser, etc
-
erdemzengindkpeak
Aug 01, 2023 12:20
I am having the same issue. How can i fix it ?
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
- 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
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Not able to reproduce this bug as both Chrome and Mac OS versions are different vs the time this bug was filed. Please re-file this bug if its an issue with Chrome version and Hardware.
Resolution Note (2023.2.X):
Not able to reproduce this bug as both Chrome and Mac OS versions are different vs the time this bug was filed. Please re-file this bug if its an issue with Chrome version and Hardware.