Search Issue Tracker
Won't Fix
Votes
2
Found in
2021.1
2021.1.15f1
Issue ID
1351701
Regression
No
[WebGL] Socket Messages being blocked when receiving Mouse Input and Frame Rate is high
Reproduction steps:
1. Open Chrome and type in chrome://flags into the URL bar
2. Search the page for "New Profiler Picker"
3. Change the drop-down menu to "Enabled"
4. Close all Chrome instances
5. Open Chrome using these args: "--args --disable-gpu-vsync --disable-frame-rate-limit"
6. Open Build Link
7. Login
8. Join Random Room
9. Ready
10. Start Game
11. Inspect incoming/outgoing socket messages
12. Hold Mouse1 and move the mouse
Expected result: Both messages are logged
Actual result: Only one of the messages is logged until Mouse1 is released
Reproducible with: 2021.1.15f1
Could not test with: 2019.4, 2020.3, 2021.2, 2022.1 (Reproduced on user hosted build)
Notes: Could not reproduce on 60hz and 144hz monitors, only reproduced on 240hz monitor
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for submitting the bug. Because this issue is only reproduced when using specific Chrome flags we will be unable to fix this explicitly. The issue seems to be related to the general performance capabilities of the browser's main message loop. Future Unity releases will include general performance improvements, so we encourage you to update the game to newer Unity versions when they're available.