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.

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

runtime: wasm: all goroutines asleep and no JavaScript callback pending - deadlock [1.11 backport] #27425

Closed
gopherbot opened this issue Aug 31, 2018 · 1 comment
Closed

runtime: wasm: all goroutines asleep and no JavaScript callback pending - deadlock [1.11 backport] #27425

gopherbot opened this issue Aug 31, 2018 · 1 comment
Labels
CherryPickCandidate Used during the release process for point releases FrozenDueToAge
Milestone
Go1.11.2

Comments

@gopherbot
Copy link

@FiloSottile requested issue #26382 to be considered for backport to the next 1.11 minor release.

@gopherbot please file this to be considered for backport to 1.11.
@gopherbot gopherbot added the CherryPickCandidate Used during the release process for point releases label Aug 31, 2018
@gopherbot gopherbot mentioned this issue Aug 31, 2018
Closed
@gopherbot gopherbot added this to the Go1.11.1 milestone Aug 31, 2018
@katiehockman katiehockman modified the milestones: Go1.11.1, Go1.11.2 Oct 1, 2018
@dmitshur
Copy link
Contributor

dmitshur commented Nov 1, 2018

Closing backport issue per Wasm backport policy; we'll not be backporting this to Go 1.11. The fix is available in master and will be available in Go 1.12.

@dmitshur dmitshur closed this as completed Nov 1, 2018
@golang golang locked and limited conversation to collaborators Nov 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
CherryPickCandidate Used during the release process for point releases FrozenDueToAge
Projects
None yet
Milestone
Go1.11.2
Development

No branches or pull requests
3 participants
@dmitshur @gopherbot @katiehockman