It is actually with the latest (1.9.2). I'll file an issue.
Thanks.
On Tuesday, December 5, 2017 at 1:51:07 PM UTC-8, Dave Cheney wrote:
>
> Can you please check if this is happening with the current version of Go
> and if so raise a bug, https://golang.org/issue/new.
>
> Thanks
>
--
You rec
Can you please check if this is happening with the current version of Go and if
so raise a bug, https://golang.org/issue/new.
Thanks
--
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
Mystery solved. It turns out it was coming from bytes.NewBuffer which was
being invoked in the method I listed. Somehow that was attributed to the
import line for bytes rather than the line of invocation.
On Tuesday, December 5, 2017 at 10:51:33 AM UTC-8, Dave Cheney wrote:
>
> No idea. Which ve
No idea. Which version of Go are you using?
--
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 http
Thanks for the pointer! I am still puzzled by the former (allocation
associated with the import line). I thought it could be an init() function
in this file, but that does not explain it...
On Monday, December 4, 2017 at 5:47:09 PM UTC-8, Dave Cheney wrote:
>
>
>
> On Tuesday, 5 December 2017 12
On Tuesday, 5 December 2017 12:09:54 UTC+11, Sangjin Lee wrote:
>
> A couple of questions on understanding go pprof's memory profile...
>
> When I list a certain function (with --alloc_objects), I see an allocation
> number associated with an import line mysteriously. I am pretty certain I
> ca
