-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: panic fatal error: malloc deadlock #24059
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
We crash in the unlikely case that we have to grow the itab table while adding an itab entry for converting |
Change https://golang.org/cl/96755 mentions this issue: |
I can confirm this CL fixes my issue. |
Reopening for cherry-pick |
CL 96755 OK for Go 1.10.1 |
Change https://golang.org/cl/102781 mentions this issue: |
… in printany They have either already been called by preprintpanics, or they can not be called safely because of the various conditions checked at the start of gopanic. Fixes #24059 Change-Id: I4a6233d12c9f7aaaee72f343257ea108bae79241 Reviewed-on: https://go-review.googlesource.com/96755 Reviewed-by: Austin Clements <[email protected]> Reviewed-on: https://go-review.googlesource.com/102781 Run-TryBot: Andrew Bonventre <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> TryBot-Result: Gobot Gobot <[email protected]>
The latest patch versions include two important fixes for the Prometheus project: * golang/go#23995 * golang/go#24059
The latest patch versions include two important fixes for the Prometheus project: * golang/go#23995 * golang/go#24059
The latest patch versions include two important fixes for the Prometheus project: * golang/go#23995 * golang/go#24059
We're still seeing issues that appear to be related on go1.10.1, should we file a separate issue or reopen? |
@SuperQ Please file a new issue. We're pretty sure this problem is fixed. I would guess that you are seeing a different problem with similar symptoms. |
faced with this type of error while was doing something like this: a function that generates a slice of func makeInt64Range(min, max int64) []int64 {
a := make([]int64, max-min+1)
for i := range a {
a[i] = min + int64(i)
}
return a
} accidentally (was distracted by random convo) it was called with mismatched boundaries: int64Range := makeInt64Range(1025, 1000) and got this:
Golang comes from: Tried that on playground: https://play.golang.org/p/D5j5EzDgNiW |
@denismakogon, please open a new issue, thanks! |
@aclements thanks, it appears that fixed was merged somewhere on the road to 1.10.2 since i don't get malloc error on the playground (which is 1.10.2). Will test on |
What version of Go are you using (
go version
)?I've bisected the issue to 2edc4d4
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?darwin/amd64
What did you do?
During development of a large internal service, we were running our test suite. The tests triggered a nil pointer dereference. On 1.9.4 the output was the usual
But on 1.10 we instead got
Some notes from trying to minimize this into a useful test case:
-test.v
, the normalpanic
output is producedpanic
output.-race
doesn't make a differenceThe text was updated successfully, but these errors were encountered: