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

fix panic in call retry gets called after a socket has been closed and the context set to nil #178

Merged
merged 1 commit into from
Sep 24, 2021
Merged

Conversation

cornelk
Copy link
Contributor

@cornelk cornelk commented Sep 23, 2021

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x56ee34]
goroutine 22 [running]:
github.com/pebbe/zmq4.(*Context).retry(...)
	/.cache/go-mod/github.com/pebbe/zmq4@v1.2.7/errors.go:95
github.com/pebbe/zmq4.(*Socket).RecvBytes(0xc00018f3e0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/.cache/go-mod/github.com/pebbe/zmq4@v1.2.7/zmq4.go:1082 +0xf4
github.com/pebbe/zmq4.(*Socket).Recv(...)
	/.cache/go-mod/github.com/pebbe/zmq4@v1.2.7/zmq4.go:1061
github.com/pebbe/zmq4.(*Socket).RecvMessage(0xc00018f3e0, 0x0, 0x2, 0x2, 0x2, 0x0, 0x0)
	/.cache/go-mod/github.com/pebbe/zmq4@v1.2.7/utils.go:115 +0x85

@pebbe pebbe merged commit 5806f25 into pebbe:master Sep 24, 2021
@cornelk cornelk deleted the fix_retry_panic branch September 24, 2021 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants