Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fatal error: all goroutines are asleep - deadlock! when using a WaitGroup with a for-select loop without an empty default case #34862

Closed
AyushG3112 opened this issue Oct 12, 2019 · 0 comments
Closed

fatal error: all goroutines are asleep - deadlock! when using a WaitGroup with a for-select loop without an empty default case #34862

AyushG3112 opened this issue Oct 12, 2019 · 0 comments
Labels
FrozenDueToAge

Comments

@AyushG3112
Copy link

What version of Go are you using (go version)?

$ go version
go version go1.13.1 linux/amd64

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN="/home/ayush/projects/gojects/bin"
GOCACHE="/home/ayush/.cache/go-build"
GOENV="/home/ayush/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/ayush/projects/gojects"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build613940075=/tmp/go-build -gno-record-gcc-switches"

What did you do?

Playground Link 1 (without default case):
https://play.golang.org/p/6VwjT-m7ZV_a

Playground Link 2 (with empty default case):
https://play.golang.org/p/CzrxcMmbKm0

What did you expect to see?

Code pasted in Link 1 should have had the same behaviour as the one in Link 2

What did you see instead?

Link 1 had a fatal crash, while Link 2 works as expected
@golang golang locked and limited conversation to collaborators Oct 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gopherbot @AyushG3112