-
Notifications
You must be signed in to change notification settings - Fork 18.1k
runtime: Invalid heap pointer on Windows 386 #9682
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
|
Please ask on golang-nuts how to debug this problem. If you don't want to find the bug, you can temporarily |
We had 4 reports on this, 3 out of 4 times it was Windows 32bit, the 4th was some storage device: No CGO involved as far as I know. Is it obvious from the traces which routine the invalid pointer is found? |
The pointer is encountered during GC, so it's hard to say where does the Normally the GC will also print one line of the form: before the panic. That is important clue. |
I am closing this for now, will try to figure out where it happens in the code first, as it seems to be 100% reproducible on the machines in question. I have a hunch that it will most likely be caused by using syscall stuff. |
There seems to be some interleaving writes, but perhaps this one makes more sense? This is go 1.4.1 on arm linux, which doesn't use cgo nor any of the syscall stuff excessively.
|
@AudriusButkevicius, do you have self-contained code to repo this? |
Sadly not, as these are all reported in the issue tracker part of the project I am working on. Everyone experiencing this seem to have 100% reproducibility, so doing a simple binary search could pinpoint to the right location. I'll see if I can get someone to do that for me. |
I would make sure that values passed back from Windows, such as HANDLEs, On Sun, Jan 25, 2015 at 1:09 PM, Audrius Butkevicius <
|
This is using go1.4.1 windows-386
The text was updated successfully, but these errors were encountered: