I've now filed https://github.com/golang/go/issues/65328 to report this.
On Friday 3 March 2023 at 09:47:26 UTC Jochen Voss wrote:
> Hi Peter,
>
> Thanks again for looking into this, and for your help!
>
> You mention that the blog post was long ago. I wonder whether the code to
> write profile
Hi Peter,
Thanks again for looking into this, and for your help!
You mention that the blog post was long ago. I wonder whether the code to
write profile information is covered by the compatibility promise. If so,
probably the legacy WriteHeapProfile function could be made to implement
the re
On Thursday, March 2, 2023 at 2:03:22 AM UTC-5 Jochen Voss wrote:
Hi Peter,
Thanks a lot, giving the "-alloc_space" option makes all the difference!
With this option, it also works for me.
I wonder whether it meant to be the way that you have to give this option.
Maybe something broke? In t
Hi Peter,
Thanks a lot, giving the "-alloc_space" option makes all the difference!
With this option, it also works for me.
I wonder whether it meant to be the way that you have to give this option.
Maybe something broke? In the blog entry https://go.dev/blog/pprof they
didn't need this opti
Jochen Voss,
On linux/amd64
xxx.go: https://go.dev/play/p/Wq_OU49LVQZ
$ go build xxx.go && ./xxx
$ go tool pprof xxx mem.prof
File: xxx
Type: inuse_space
Time: Mar 1, 2023 at 11:03pm (EST)
No samples were found with the default sample value type.
Try "sample_index" command to analyze different
Try commenting runtime.GC
On Wed, Mar 1, 2023, 14:31 Jochen Voss wrote:
> Dear Sean,
>
> Thanks for trying this out. Your result is different from mine, but I
> don't think this can be right. According to the output, the only
> allocation would be inside the regexp module. But there should be
Dear Sean,
Thanks for trying this out. Your result is different from mine, but I
don't think this can be right. According to the output, the only
allocation would be inside the regexp module. But there should be many
more allocations (for example in line 56 of the code)!
All the best,
Joche
fwiw, that code works on my machine :tm:
1:40:47 ~/tmp/testrepo0120 0:00:27
main » go run .
1:40:58 ~/tmp/testrepo0120 0:00:08
main » go tool pprof mem.prof
File: testrepo0120
Type: inuse_space
Time: Mar 2, 2023 at 1:40am (CST)
Entering interactive mode (type "help" for commands, "o" for options)
The problem also occurs on AMD64 Linux, so it's not architecture specific.
Hints would be most welcome!
On Wednesday, 1 March 2023 at 13:55:30 UTC Jochen Voss wrote:
> Dear all,
>
> I'm trying to profile memory use of a program, following the instructions
> at https://go.dev/blog/pprof , but I
