-
Notifications
You must be signed in to change notification settings - Fork 712
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
App panic on concurrent map writes (0aaacc2) #1094
Labels
bug
Broken end user or developer functionality; not working as the developers intended it
Comments
It's crashing here Line 189 in 0aaacc2
And it seems that Go 1.6 is panicking after detecting a race:
Here's a longer excerpt of the code func mapassign1(t *maptype, h *hmap, key unsafe.Pointer, val unsafe.Pointer) {
if h == nil {
panic("assignment to entry in nil map")
}
if raceenabled {
callerpc := getcallerpc(unsafe.Pointer(&t))
pc := funcPC(mapassign1)
racewritepc(unsafe.Pointer(h), callerpc, pc)
raceReadObjectPC(t.key, key, callerpc, pc)
raceReadObjectPC(t.elem, val, callerpc, pc)
}
if msanenabled {
msanread(key, t.key.size)
msanread(val, t.elem.size)
}
if h.flags&hashWriting != 0 {
throw("concurrent map writes")
}
h.flags |= hashWriting
alg := t.key.alg
hash := alg.hash(key, uintptr(h.hash0))
if h.buckets == nil {
h.buckets = newarray(t.bucket, 1)
} |
2opremio
changed the title
App version 0aaacc2 crashing
App panic on concurrent map writes (0aaacc2)
Mar 2, 2016
2opremio
added
the
bug
Broken end user or developer functionality; not working as the developers intended it
label
Mar 2, 2016
@errordeveloper Can you please paste a gist with the full backtrace (i.e. including all the goroutines). I believe it will reveal who is accessing the map concurrently. |
Probably a duplicate of #1087 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: