Surprised that some call-sites are split

[sfiruch]

Context

I notice from time to time that sometimes a called function is split into two nodes in the call tree and flamegraph. Here's one example, which I'm confused by.

The RequestSum method contains a single call to LoadTreeFromSession. There's only a single call-site, and it's always using the same parameters.

Here's the public profile:
https://share.firefox.dev/40IzYpz

Question

Is this expected or a bug? Can I prevent it from happening?

[mstange]

Seems unexpected to me. It probably means that ConvertMethod created two different funcTable entries for this method. I would expect a single funcTable entry, and potentially different frameTable entries using that same func.