This repository has been archived by the owner on Oct 20, 2024. It is now read-only.
Fix an "unrecognized selector sent to instance" crash #79
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An app using
PocketSocket
crashes occasionally with this information:The
notifyDelegateDidFlushOutput
function checks if the delegateresponds to the
webSocketDidFlushOutput:
selector before sending it.The only possible cause for the crash is when the delegate changes
between the check and the call because the function is not atomic. Added
testChangingDelegateWhileFlushingOutputShouldNotCrashWithUnrecognizedSelector
can reproduce the crash very quickly and consistently.
The fix here is to capture the delegate strongly while the function is
running to work with the same instance. The patch fixes the crash in all
similar places in
PSWebSocket
, as well as inPSWebSocketServer
.