How to profile the editor during extreme enter/exit playmode waits?

Ran into a situation where the enter and exit times are ludicrously extreme, i could theoretically profile this with the standalone profiler attached to the editor. Problem is that after a 10 minute exit time, when the profiler resumes it Zooms at the speed of sound past the point where the issue was.
I’m unable to allocate enough frames due to RAM / diskspace constraints, 16gb RAM + 55gb pagefile isn’t enough for the profiler to have a chance of catching what is causing my headaches.

Is there some way to make the profiler freeze X frames after crossing some user defined threshold Y, this would be a nice feature even for play mode to have the option of automatically pausing the play mode if some user defined threshold is exceeded. But for me this would be a necessity to even be able to make a rational bug report, Hey this bar here is taking ages isn’t exactly an easy to follow up bug report :slight_smile:

Hello there,

The Editor Iteration Profiler might help you in this it only records the domain reload & enter/exit Playmode times. Alternatively you can write a script that will record the data to a .raw profiler data file and stop recording a couple of frames after entering playmode. The Profiler.logFile API docs should help you get started on that

Thanks i’ll give it a shot!

1 Like