Profiler.BeginSample/EndSample error request

In a future release, could the error about non-matching profiler BeginSample and EndSample counts point towards which file/line in which the mismatch is occurring? We just noticed this error sometime in the past few weeks. We're not exactly sure when it started, we don't know where the mismatch is, and the error gives absolutely no information. The entire error is just: "Non matching Profiler.EndSample (BeginSample and EndSample count must match)"

It wouldn't be a big deal, except that when we get this error, the profiler stops showing any and all data/graphs, effectively making the profiler useless. There's no telling where the mismatch could be; we have a ton of code spread throughout thousands of scripts, many of which make use of the profiler samples. It can take ages to track this sort of thing down. Putting some additional information in this error message would be immensely helpful.

 

^this.
We also have the same error and don't know where the hell it comes from. I'd guess it's from some loading routine as it only happens in between our scenes. I also feel like it's responsible for some of our crashes.

 

I too have this problem.

 

I went through the entire scripts and I have never used Profiler feature, yet I have this error popping up from time to time if profiler is open. The profiler still works though. But it is very annoying indeed.

 

Same here. It would be very useful to know, especially as I don't use the Profiler class in my own code.

 

I disabled the VSync in the Profiler window and this error disappeared

 

Yep! That works. Just disable vsync. The tiny little square on the left of CPU Usage

 

Be sure you use it inside main thread! Found here:
"Cannot may be executed in coroutines or separate threads. Be aware that if you will decide to move your code to a separate thread, you shouldn’t call Unity API from within that thread. Instead you should use components like Dispatcher from UnityToolbag that will dispatch Unity API calls to the main thread."

 

This may be outdated, according to this it should be thread safe as of 2018.2
https://forum.unity.com/threads/profiling-background-threads.521196/