The pprof heap profile is somewhat useful, but it only narrows things down to which function/method is doing the allocating - not which objects are in memory.
debug.WriteHeapDump() can be used to get more detailled stats - it would be good to allow triggering this via gops too