Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2020.2.0a5
Issue ID
1230538
Regression
Yes
[Profiler] Building with Autoconnect Profiler enabled throws exception that "Non matching profiler.EndSample"
Non matching Profiler.EndSample exception is thrown on Build and Run when Autoconnect Profiler is checked on
Steps to Repro:
1. Open attached project
2. Build Setting > Development Build > check on
3. Build Setting > Autoconnect Profiler > check on
4. Build and Run
Expected Result:
No errors in the console
Actual Result:
Non matching Profiler.EndSample exception is thrown
Reproducible on: 2020.2.0a5
Working fine on: 2020.2.0a4, 2020.1.0b3, 2019.3.6f1
Environment: Windows 10 only
Stack trace:
Non matching Profiler.EndSample (BeginSample and EndSample count must match): PostLateUpdate.ProfilerEndFrame
Previous 5 samples:
Profiler.SerializeStats
Profiler.CollectGIStats
Profiler.CollectUICanvasStats
Profiler.CollectPhysics2DStats
Profiler.CollectPhysicsStats
In the scope:
<Root>
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2020.2):
Bug is fixed