Search Issue Tracker
Fixed in 5.5.0
Votes
1
Found in
5.5.0b4
Issue ID
837018
Regression
Yes
Non matching Profiler.EndSample (BeginSample and EndSample count must match) is thrown in the Development console
Steps to reproduce:
1. Open the attached project
2. Open the ProfilerMismatch.unity scene
3. Build the attached project(build for windows x86_64, development build, Atoconnect profiler)
4. Run the built project
5. Observe error messages in development console:
Non matching Profiler.EndSample (BeginSample and EndSample count must match)
Expected result: Running without errors
Actual result: Development console printing error messages
Reproduced with: 5.5.0b4, 5.5.0b5, 5.5.0b6
Not reproduced with: 5.5.0b3
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
- [VFX] Missing Expand Toggle with Output Slot
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
Sandip_Artoon
May 17, 2017 08:40
This is still happen in unity 5.5.2f1
grimmy
Apr 25, 2017 13:27
I just started getting this with 5.5.1p4 :(
ask2asim
Apr 06, 2017 08:43
This is still a problem in Unity 5.5.3f1
theolagendijk
Mar 20, 2017 14:11
Please reopen, because this is still an issue in Unity 5.5.2p3.
atmosgames
Mar 17, 2017 01:05
This is still a problem.
This was just thrown in my console: Non matching Profiler.EndSample (BeginSample and EndSample count must match)
atmosgames
Mar 17, 2017 01:05
This is still a problem.
This was just thrown in my console: Non matching Profiler.EndSample (BeginSample and EndSample count must match)
AlbertMN
Mar 14, 2017 15:14
I too confirm that this problem is still here in 5.5.2f1
KrzysztofPieta
Mar 13, 2017 14:58
Confirming that this bug is still reproduced on 5.5.2f1
kip_one
Mar 06, 2017 10:58
Reproduced with 5.5.0p4
Please reopen this issue
samuel-levine
Mar 01, 2017 14:41
We really could use a "vote to reopen" button for unresolved issues like this one.