Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upPrometheus crashes and hangs on `fatal error: found bad pointer in Go heap (incorrect use of unsafe or cgo?)` #2263
Comments
ichekrygin
changed the title
Prometheus crashes and hangs on `*(object+560) = 0x0 *(object+568) = 0x0 *(object+576) = 0x0 *(object+584) = 0x0 *(object+592) = 0x0 *(object+600) = 0x0 *(object+608) = 0x0 *(object+616) = 0x0 *(object+624) = 0x0 *(object+632) = 0x0 fatal error: found bad pointer in Go heap (incorrect use of unsafe or cgo?)`
Prometheus crashes and hangs on `fatal error: found bad pointer in Go heap (incorrect use of unsafe or cgo?)`
Dec 7, 2016
This comment has been minimized.
This comment has been minimized.
|
This is likely a bug in Go. What version of Prometheus is this, and what version of Go was it compiled with? |
brian-brazil
added
the
kind/bug
label
Dec 7, 2016
This comment has been minimized.
This comment has been minimized.
|
@brian-brazil, sorry keep hitting |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
This comment has been minimized.
This comment has been minimized.
|
Doesn't look like there's any known issues in 1.7.3, so this is something new. |
This comment has been minimized.
This comment has been minimized.
|
Could also be an edge case in goleveldb, which certainly uses the |
This comment has been minimized.
This comment has been minimized.
|
Hi, any progress on this issue? |
brian-brazil
added
priority/P2
help wanted
labels
Jul 14, 2017
This comment has been minimized.
This comment has been minimized.
|
Are you still seeing this? This has been stale for sometime and with the new 2.0 release coming up, this becomes obsolete. Closing this now, but feel free to re-open if you are still facing this in |
gouthamve
closed this
Sep 28, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
ichekrygin commentedDec 7, 2016
•
edited
What did you do?
Run Prometheus on K8S
What did you expect to see?
Prometheus is running w/out down time
What did you see instead? Under which circumstances?
Prometheus has crashed on:
Even on crash, I would expect
Prometheusprocess to exit and let K8S handle the restart, instead, it appears the process just hung.Environment
Kubernetes on AWS (CoreOS)
System information:
insert output of
uname -srmhereLinux 4.7.3-coreos-r2 x86_64Prometheus version:
insert output of
prometheus -versionheren/a
Alertmanager configuration file:
N/A
Logs:
attached