ticker.Reset can cause SIGSEGV segmentation violation

[gnvk]

Go version

go version go1.23.1 darwin/arm64

Output of go env in your module/workspace:

GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/gnvk/Library/Caches/go-build'
GOENV='/Users/gnvk/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/gnvk/Dev/go/pkg/mod'
GONOPROXY='github.com/alpacahq/*'
GONOSUMDB='github.com/alpacahq/*'
GOOS='darwin'
GOPATH='/Users/gnvk/Dev/go'
GOPRIVATE='github.com/alpacahq/*'
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/opt/homebrew/Cellar/go/1.23.1/libexec'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/opt/homebrew/Cellar/go/1.23.1/libexec/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.23.1'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/Users/gnvk/Library/Application Support/go/telemetry'
GCCGO='gccgo'
GOARM64='v8.0'
AR='ar'
CC='cc'
CXX='c++'
CGO_ENABLED='1'
GOMOD='/Users/gnvk/Dev/alpaca/bt/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/xv/5sz1kn411vb_g2_vmhnstl1c0000gn/T/go-build1871065581=/tmp/go-build -gno-record-gcc-switches -fno-common'

What did you do?

After a some investigation I finally managed to reproduce a strange SIGSEGV: segmentation violation error.

package main

import "time"

type timeTicker struct {
	time.Ticker
}

func main() {
	t := timeTicker{
		Ticker: *time.NewTicker(time.Second),
	}
	t.Reset(time.Second)
}

What did you see happen?

Running the above program with go 1.22 exits with 0. With go 1.23 it crashes with

fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x10499b8dc]

and a goroutine trace. In this reproducible example it's obvious from the stack trace that the segfault is caused by the ticker.Reset call, but this was not the case in the original!

What did you expect to see?

Exit 0.

[gabyhelp]

Related Issues and Documentation

• time: Ticker.Reset(0) deadlocks #49315 (closed)
• Fatal error: runtimer: bad p when resetting the value of a ticker pointer #45008 (closed)
• Lockup in time.stopTimer #5745 (closed)
• time timer.Reset is not thread safe #26741 (closed)
• runtime: SIGSEGV in the new timer code #35367 (closed)
• time: zero value of time.Timer crashes confusingly #8776 (closed)
• runtime: TestSegv fails with the latest tip version #49192 (closed)
• runtime: `SIGSEGV` via go test with -race -cover and -tags netgo on alpine linux/arm64 #59369
• runtime: unexpected signal during runtime execution - segmentation violation SIGSEGV #46666 (closed)
• SIGSEGV: segmentation violation code=0x1 - help #49992 (closed)

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[seankhliao]

Duplicate of #69186