Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.4.0a6
Issue ID
753097
Regression
No
If you leave Editor in Play mode for 1 hour - it will give error "The profiler has run out of samples for this frame..."
What happened
If you leave Editor in Play mode for 1 hour - it will give error about profiler. But I didn't even open Profiler at all.
How we can reproduce it using the example you attached
1 Open attached project and press Play
2 Leave Editor in Play mode for about 1 hour
Actual result: error appears in Console:
"The profiler has run out of samples for this frame. This frame will be skipped. Increase the sample limit using Profiler.maxNumberOfSamplesPerFrame"
Comments (3)
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
alexandru-ivan-daniel
Dec 12, 2016 09:25
The exact steps that MBCAULEY mentioned i'm getting the same problem i used it for a little cause i had some memory usage issues but right after i was done using it i started getting this error: "The profiler has run out of samples for this frame. This frame will be skipped. Increase the sample limit using Profiler.maxNumberOfSamplesPerFrame" even though i wasn't even using the profiler how can i get rid of this ?
Thelo
Nov 16, 2016 17:41
Here is a forum thread about this problem, which has in fact never been fixed as of 5.4.2f2:
https://forum.unity3d.com/threads/the-profiler-has-run-out-of-samples.321918/
mbcauley
Oct 04, 2016 22:08
I get this same issue in Unity 5.4.1f1 (as well as previous releases) if I open the Profiler up, use it for a little while, and then close it. Inevitably the error always seems to pop up unless I quit Unity with the Profiler window closed and reopen my project.
I have tried to "Clear" the Profiler before I close the window and I still get the error.