go: runtime: memory corruption on darwin/amd64
#!watchflakes
post <- goos == "darwin" && goarch == "amd64" && (
log ~ `fatal error: found pointer to free object` ||
log ~ `fatal error: found bad pointer in Go heap` ||
log ~ `fatal error: workbuf is not empty` ||
log ~ `schedule: holding locks` ||
log ~ `fatal error: bad summary data` ||
log ~ `fatal: morestack on gsignal` ||
(log ~ `panic: runtime error: invalid memory address or nil pointer dereference` && log ~ `^\s*runtime\.sigpanic.*\n\s+.*\n\s*runtime\.sweepone`) ||
(log ~ `SIGSEGV: segmentation violation` && log ~ `^\s*runtime\.spanOfUnchecked\(`))
Issue created automatically to collect these failures.
Example (log):
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 27 (11 by maintainers)
These represent more general runtime memory corruption, but I suspect this is all part of the same issue.
2023-08-21 23:20 darwin-amd64-11_0 go@e3c80f57 cmd/go.TestScript (log) 2023-08-22 08:38 darwin-amd64-longtest go@05f95115 runtime.TestEINTR (log)
I was going back through issues assigned to me (oops, I have a backlog) and I noticed that #58715 is also memory corruption, but none of those failures include forkExec. Just mentioning it here since it might be related.
We should probably aggregate such issues into a single issue.