Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.6.0f3
Issue ID
901252
Regression
Yes
[WebGL] Profiler does not work Build&Run's tab is closed and then reopened
To reproduce:
1) Create new project
2) Mark it to Autoconnect to Profiler (it doesn't work when directly connecting)
3) Build and run for WebGL
4) Notice player connects to profiler and profiling data is gathered and shown to user
5) Close tab
6) Open new tab and go to same localhost that was generated for first time
Expected: Profiler works again once loaded
Actual: Player is shown as autoconnected but no data is outputed
Tested on Chrome and Firefox
Not reproduced in 5.5.3p1 (Connection is shaky and it can sometimes drop mid-session when losing/regaining focus, but it would always connect at start)
Reproduced in 5.6.0f3, 2017.1.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes when loading RenderDoc with Graphics API set to OpenGLES2 or OpenGLES3
- [Windows] Development Build with no scenes shows a purple screen when using OpenGLES3 graphics API
- Shader variants take too much memory at runtime
- [HDRP][VFX] Output mesh with default shader is incorrectly sorted before the HDRP fog
- Error "'GamepadSpeakerOutputType' does not exist in the namespace 'UnityEngine'" occurs in the Console when building a project
Add comment