I can run it once or twice but if I forget to clear it out before the 2nd or 3rd time i run my game I get a unity crash.
yea profiler seems to have some crasing issues. but i only noticed it when deep profiling is on
Yeah, profiler is kinda slow and can’t handle a lot of data which leads it to crash very often… It’s annoying.
yes using the profiler scrubbing through its timeline a bit… and next thing unity will most definitely crash shortly thereafter… seems to be a 100% guaranteed thing for me now in 2 different projects using 5.6b11.
I think there are some leaks in it, but the crashes and errors seem mostly avoidable. I do a lot of profiling and noticed that it doesn’t do well if you leave it unattended for long periods or simply leave it as a background tab and since I’ve been managing it closer I’ve had no issues.
- Toggle off Record when not using it.
- Don’t use Deep Profile if regular Profiling gets you there. Some things produce thousands upon thousands of data points per frame and this can generate some serious overhead which can very easily lead to crashes.
- Close the tab when done with it. I’ve noticed crashes specifically when the profiler is open for a very long time and record is on, but I’m not using the tab. I’ve also noticed errors linked to it in the console when its sitting in a background tab.
Oh it’s definitely got problems, I don’t think just to tip toeing around it by doing any of those things is gonna help one bit, especially as I’ve never had to in the past. And I don’t recall having this amount of profiler crashes like this often in earlier 5.6 betas.
And yeh deep profiling still sucks, I avoid using it most the time with more profiler samples instead. Though honestly thought they would have improved deep profiling in 5.6, but its still a pain in the ass to look at timeline snapshots.
Have you considered that maybe your application has changed over time, and therefore contributed to the instability of the profiler?
Hi Player7,
Thanks for reporting your issues! We know about the problems with the profiler and they have already been fixed. The fix should be available in an upcoming release.
Well glad someone found the steps to reproduce it, all I know is that using the profiler would definitely result in a crash soon after in these later beta’s. I skipped few betas and only been using 6,9,10,11 and the profiler crashing has been very apparent where it wasn’t before b6 so yeh.
well 5.6.0f1 is not the upcoming release with this issue fixed then…as its still crashing… so another week then 