On 14 February 2018 at 16:15, Kane Kim <kane.ist...@gmail.com> wrote:
> If we don't use CGO all memory should be reported somewhere? > Well, assuming no part of your software calls mmap, or there isn't something else funny going on. Can you capture when this large region is mapped with strace? At what point in the process lifecycle does this happen? Perhaps you can use a debugger (dlv) to catch the culprit in the act. Perhaps you could come up with a mechanism to unmap the region and get a segfault and stacktrace when the culprit tries to use it. If you find out what's going on please share if you can, it sounds like an interesting issue. -- 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.
