Skip to content

Conversation

markdrayton
Copy link

Currently the check to see if a connection was canceled happens after
newConn() is called, leaking a goroutine waiting to receive on chInPkt.
Move the check up.

Closes #77.

Currently the check to see if a connection was canceled happens *after*
newConn() is called, leaking a goroutine waiting to receive on chInPkt.
Move the check up.
@markdrayton
Copy link
Author

Whoops, sorry for the duplicate PR. I fixed a typo in my branch name and didn't expect this to close the first PR for me (though that makes sense in hindsight).

@estutzenberger estutzenberger merged commit 3abdc48 into go-ble:master May 19, 2021
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.

Leaking goroutines in Conn.recombine()?
2 participants