kedi maması köpek maması www.patilimama.com

Don't just close the profiler, stop "recording" first.

I want to add that I mistakenly thought that closing the profiler stops "recording" but I'm getting mixed results. I find things run much smoother if I remember to stop recording before closing the profiler window.

Found a Solution. just unclick the very small square icon in the profiler : Others

This is happening to me in version 2017.1.1f1

Same here ! Please fix this...

To get around the issue skewing our profiling, we're just automatically clearing the profiler whenever it gets into this state. You can do the same thing by sticking this in an Update() loop:

if (UnityEditorInternal.ProfilerDriver.firstFrameIndex > 0)
{
UnityEditorInternal.ProfilerDriver.ClearAllFrames();
}

This seems to happen on the same frame that UnityEditorInternal.ProfilerDriver.firstFrameIndex becomes greater than 0, which reinforces the idea that it's a bug related to Unity accruing more profiler frames than it can hold in a single buffer.

same Profiler.FinlazeAndSendFrame takes81.2% since i updated to 2017.1.1f1

I still found the issue in version 2017.1.0p5.

+1. On 2017.1.0f3, triggering when the window is full of samples and goes back to behaving when I hit clear.