Digging deeper in profiler GC.Alloc

Unity Engine
,
1

Hi,

My main PlayerLoop looks like this now, Im zoomed in quite a bit but the whole thing is just a large amount of GC.Alloc from start to finish:

6501914--732218--upload_2020-11-8_13-14-33.png
6501914--732218--upload_2020-11-8_13-14-33.png1519×654 66.1 KB

This is the zoomed out view:

6501914--732221--upload_2020-11-8_13-14-44.png
6501914--732221--upload_2020-11-8_13-14-44.png1518×623 67.3 KB

If I read this correctly the PlayerLoop still takes up 80ms to do all the calculations, but I have trouble identifying exactly why.

When zooming in all I can see are a bunch of GC.Allocs spread out with plenty of idle time between them.

How can I figure out exactly what is causing the Allocs and how can I figure out why there is so much idle time going on here?

6501914--732215--upload_2020-11-8_13-12-49.png
6501914--732215--upload_2020-11-8_13-12-49.png1920×1080 318 KB

2

You could try to use deep profile to get more info.
Also it may be useful to use Hierarchy view to get info about which method trigger GC.Alloc

3

Thanks a bunch, I didn’t notice the option for a deep profile =)

It is now immediately clear that my problem is within my string based command parser logic. This is all I needed to know =)

6501959--732230--upload_2020-11-8_13-42-0.png
6501959--732230--upload_2020-11-8_13-42-0.png1332×444 33.9 KB

6501959--732233--upload_2020-11-8_13-43-10.png
6501959--732233--upload_2020-11-8_13-43-10.png1139×215 35.6 KB

1 Like
4

Also, If you just need to see more details of where the GC.Allocs come from, you can turn on Call Stacks, record and then select these GC.Alloc samples. The CPU Usage Profiler Module manual page has more details on this.