Why go heap profiler shows significantly less total memory than MemStats.HeapAlloc?

Question

I'm trying to investigate a memory leak in our service. And for some reason, while HeapAlloc grows up to 3.7gb, pprof heap profiler explains only 2.4gb. What is that 1.3gb space for?

I thought, that HeapAlloc memory is exactly what heap profiler should describe.