> It's a plausible mistake from any old Unix hand, I think. anecdotally, i ran into this very same issue yesterday when trying to instrument a 1.10 go program that allocated (but never used) more than 512 gigabytes of memory. i put in the memprofile saving code as a deferred closure in main and hit ctrl+C at the crucial moment expecting a memory profile to be generated, only to see nothing :)
-- 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.
