Search Issue Tracker
Fixed in 5.5.0
Votes
1
Found in
5.3.1p2
Issue ID
759492
Regression
No
[WebGL] Autoconnecting project to profiler locks up browser periodically
To reproduce:
1) Create new project
Optional: Create a moving cube to better see when it freezes
2) Change platform to WebGL
3) Enable 'Development build' and 'Autoconnect to Profiler' options in Build settings
4) Build and run
5) After 15-60 seconds the browser becomes not responding.
Notes: Sometimes the browser unstucks itself after some time, or if on Firefox, when this prompt appears ( http://i.imgur.com/mNOvz8P.png ), click Continue and it will work again until next freeze up. Trying to debug loads up this - http://i.imgur.com/BRI5CqY.png - but the browser still becomes unresponsive from time to time.
Doesn't happen in Android IL2CPP build
Tested and fails on:
-Windows
--Firefox 45, 43.0.2, 40.0.2, 37.0
--Chrome 48, 50,
--EdgeHTML 13
-OSX
--Chrome 50 (after several minutes)
Works well with latest Safari + FF on OSX.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment