runtime: windows 10 amd64 1.22.0 goroutine output "exit status 0x40010004"

[caisi35]

Go version

go 1.22.0

Output of go env in your module/workspace:

set GO111MODULE=
set GOARCH=amd64
set GOBIN=      
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GONOPROXY=*.corp.example.com
set GONOSUMDB=*.corp.example.com
set GOOS=windows
set GOPRIVATE=*.corp.example.com
set GOPROXY=https://goproxy.io,direct
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOVCS=
set GOVERSION=go1.22.0
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=0
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config

What did you do?

package main

import (
	"fmt"
	"time"
)

func main() {

	done := make(chan error, 1)
	go func() {
		time.Sleep(time.Second * 6)
		done <- fmt.Errorf("go err")
	}()
	select {
	case err := <-done:
		fmt.Println("error", err)
	case <-time.After(5 * time.Second):
		fmt.Println("timeout")
	}
	fmt.Println("end")
}

go run main.go

What did you see happen?

output:
exit status 0x40010004

What did you expect to see?

output:
timeout
end

[gabyhelp]

Related Issues and Documentation

• exit status 0xdeaddead #54067 (closed)
• Can differed calls run after runtime.Goexit() in a given goroutine ? thanks #43952 (closed)
• go run #50336 (closed)
• test001 #53494 (closed)
• go command #62170 (closed)
• test #61922 (closed)
• go env #35453 (closed)
• A goroutine problem? #32513 (closed)
• buildmode #57437 (closed)
• im going to go #53597 (closed)

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

[seankhliao]

I think it's something in your environment killing the processes, not something the Go project can help with.