The profiler has run out of samples for this frame. This frame will be skipped.

Unity Engine
1

Anyone else getting this msg a lot since beta 15? It appears at random times when I’m not profiling. It even appears when I turn off “Record” in the profiler, though I’ve noticed that “Record” is often switched on again after some time when I reopen the profiler.

2

I’m seeing this message a lot in logs with beta 14 when I don’t have the profiler window open, with standalone builds. I also get this log message a lot:
Skipping profile frame. Reciever can not keep up with the amount of data sent

(Filename: C:/buildslave/unity/build/Runtime/Network/PlayerCommunicator/GeneralConnection.cpp Line: 339)

3

If I have a standalone player (with Development Build checked) running on the same machine as Unity Editor, I noticed that my Windows Resource monitor reports the standalone build sending an additional 10 MB/sec and the Unity Editor receiving an additional 10 MB/sec. This holds even if I have the profiler window closed and the Record button in the profiler window disabled. I have no game running in the Unity Editor during these tests.

If I make my standalone build without Development Build checked, I do not notice the additional 10 MB/sec in local network traffic.

4

I’m also getting the ‘The profiler has run out of samples for this frame. This frame will be skipped.’ error on b18

It has started happening fairly consistently now at one particular stage in game, regardless of whether or not I have the profiler open in editor.

Also happens in stand alone windows build. Or at least the game hangs for around a second at the exact same point I get the error in editor. This happens if development build is checked and also when it isn’t.

The error in editor is annoying but manageable. Getting the freeze in stand alone build is infuriating!!

Surely there is some way of turning it off properly in stand alone?!?

5

I’m getting it as well in 5.0.0f2. I didn’t notice it happening until I did my first profiling run, then even after I closed the profiling window or restarted the editor, I kept getting them.

6

happening to me in b22 as well. started after my first profiling run.