Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
runtime: sigpanic during GC on android/arm64 #22204
What version of Go are you using (
I found another crash report from golang1.8 which is slightly more interesting, but ultimately also happening when accessing heap spans.
I keep coming back to this issue and not making any progress. I just don't see how this can happen.
@tmm1, do you happen to get (or can you get) core dumps from any of these? I'd love to see the memory map at the time of the crash.
My initial hunch was that we needed a memory fence between mapping spans and updating
I tried looking for patterns in the faulting addresses, but didn't turn up much. The heap layout should be:
Which means the first three faults correspond to
None of these are on any obvious boundaries.
The good news is Go 1.11 almost certainly can't have this problem because I've completely rewritten all of the code involved (https://golang.org/cl/85887).