Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2019.1.0a2
2019.1.0a12
Issue ID
1110746
Regression
Yes
[Profiling] "Non matching Profiler.EndSample" exception is thrown on quitting a standalone player development build
"Non matching Profiler.EndSample" exception thrown on quitting a standalone player development build with autoconnect profiler checked. Refer the video for details.
Step to reproduce:
1) Create a new project.
2) File > Build settings
3) Check development build > Check autoconnect profiler
4) Build and run
5) Launch the standalone build and verify the profiler data is displayed in profiler window > Quit the standalone build
Actual result: "Non-matching Profiler.EndSample" exception is thrown in the console.
Expected result: The standalone build quits gracefully and no exceptions occur in the console.
Occurs in: 2019.1.0a12, 2019.1.0a2
Works fine in: 2018.3.0f2
Note: Profiler data is not displayed in 2019.1.0a1
Environment: Both Windows and Mac
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
Add comment