Search Issue Tracker
Fixed in 2017.1.0f3
Votes
0
Found in
5.6.0b3
Issue ID
867091
Regression
Yes
Profiler is not displaying any data when profiling Development Build
To reproduce:
1. Open any project. (If you create a new project, then also create a scene for the build).
2. Go to "Build Settings" and build a Standalone Windows build, with "Development Build" and "Script Debugging" checked.
3. Open "Profiler" window.
4. Play built game in windowed mode.
5. Go to your "Profiler" and in "Active Profiler" select "WindowsPlayer".
Expected result: Profile window should display profiling samples as in earlier Unity versions.
Actual result: No data is displayed.
Reproducible with: 5.6.0a1, 5.6.0b3
Not reproducible: 5.5.0p3
Note:
Warning "Sending message header failed" is displayed even in 5.5 version, where profiler is working as expected, when you close the standalone Player.
Comments (1)
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
Kerosini
Feb 12, 2017 20:37
Reproducible with 5.5.0f3 but with 5.5.1f1 every thing is fine :)