The reporter sends SIGQUIT 100 ms after start to a child process built with -race that keeps starting bursts of goroutines, and counts the outcomes. Instead of the usual all-goroutine dump, the child sometimes dies with fatal error: unsafe.Slice: len out of range or hangs (darwin/arm64), or segfaults (linux/amd64). The report lists go1.27.4 darwin/arm64 and go1.27.2 linux/amd64 as affected and reproduces it at tip (2026-11-14). Go 1.26.0 is affected and Go 1.25.0 is not. On darwin, the signal was seen to land while the race runtime was in a kernel call made as a goroutine started or exited. Gopherbot has linked CL 863961, "runtime: don't hexdump a frame that is not on the stack". The issue is labelled compiler/runtime with no milestone yet. The reporter says AI assistants helped with the investigation and the patch.
kill -QUIT (or Ctrl-\) is the standard way to see where a stuck Go service or test is blocked, and -race builds are exactly what runs in CI when a test hangs on a deadlock. On Go 1.26+, a missing or garbled dump from a race build may be this runtime bug rather than your code. Until the CL lands, rerun without -race, or use GOTRACEBACK=all with a test timeout (go test -timeout already prints all goroutines).