As the title suggests, the profile output from go pprof only records the function stack where objects are created, but it doesn't provide information about object reference relationships. I would like to generate a flame graph that can quickly locate the GC roots and reference chains for a heap object that is causing significant memory leaks. This would help in identifying the memory leak issue more effectively.
As the title suggests, the profile output from go pprof only records the function stack where objects are created, but it doesn't provide information about object reference relationships. I would like to generate a flame graph that can quickly locate the GC roots and reference chains for a heap object that is causing significant memory leaks. This would help in identifying the memory leak issue more effectively.