Keith Randall
Keith Randall
Thanks for the bug report. Yes, the heap dump parser needs some hardening for dwarf info coming from non-Go sources. It doesn't always conform to the invariants the reader expects....
Yes, since 1.4 there just isn't enough type info recorded by the runtime during allocation. The heap dump contents reflect that. We're moving to a new model where functionality like...
The standard Go issue tracker can be used to report issues. For just discussion (questions, etc.) you can use the golang-nuts mailing list. Or mail me directly. See https://golang.org/project/ for...
Thanks for the bug report. It looks like there is some incomplete dwarf information; some dwarf entry has no name. I don't see how that could have happened, at least...
That is probably the issue then. Those c libraries don't contain dwarf information that is as clean as the hview tool would like it. I've pushed a simple bug fix...
Not super excited about it. There's no hurry; it can live here indefinitely. I'd like to see the ecosystem for MacOS on arm64 develop a bit more to see where...
@borzovplus The fix will be available in 1.19.1 when it comes out (a few weeks). I'm not sure about whether this will be fixed in 1.18 or not. @mdempsky
Appending to a global variable without synchronization is a data race. Have you tried running with the race detector?
The race detector uses ~10x the memory that a run without `-race` uses. Are you actually running out of memory? How much memory does a regular run use? It is...
Hm, I don't know then. You have officially overreached my Windows knowledge :(