Hi all, We've been trying to track down a nasty memory allocation issue (i.e. a leak somewhere) for the past few months and mostly failed. A few times we thought to create a heap profile to see where the memory is at, but the heap profile only tells us where the memory was allocated (I can answer that myself too, in the network routine that receives the data from remote machines); but not where the data is being still referenced.
Does anyone know of a profiling mode or tool which could allow me to investigate the "weights" of different live objects? IT would help immensely to see which object is hogging/leaking references to our supposedly not-used-anymore data. Thank you, Peter -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
