Any chance you have the stacks? Was this one a 386 machine, or on Windows
perhaps?
Thanks in advance.

On Mon, Mar 16, 2015 at 5:59 AM, trywen notifications@github.com wrote:

runtime: garbage collector found invalid heap pointer
*(0x1a737ea0+0x0)=0x30 s=nil
runtime: found *(0x2edc55f0+0x8) = 0x1a737ea0+0x0

see #9872 #9872

—
Reply to this email directly or view it on GitHub
#10175.

system is windows 7, go is 1.4.2

Thanks, I'll assume this is a 64 bit machine so we can rule out
#9872. The GC is seeing the value 0x30
that it has been told is a pointer and it is not. This could well be
related to #9125 in which case could
you make sure that the 0x30 is not being returned from Windows and
incorrectly typed as a pointer.

On Mon, Mar 16, 2015 at 12:42 PM, trywen notifications@github.com wrote:

system is windows 7, go is 1.4.2

—
Reply to this email directly or view it on GitHub
#10175 (comment).

Can you make this happen again?
We need the full stack trace for the garbage collector reporting the crash in order to make any progress at all here. Ideally I'd like to see the stacks of all the goroutines in the dump.

If you can get that information, please file a new bug. Thanks.