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

Segfault on OS X #51

Closed
sarahhodne opened this issue May 18, 2012 · 3 comments
Closed

Segfault on OS X #51

sarahhodne opened this issue May 18, 2012 · 3 comments

Comments

@sarahhodne
Copy link

Hey,

Seems like libPusher segfaults on Snow Leopard. The full crash report can be found here: travis-ci/travis-watcher-macosx#3.

Seems like this could be caused by an instance of SRWebSocket not being retained. Looking at the code, it seems like the SRWebSocket instance is just being assigned to an instance variable, which to the best of my knowledge does not retain the instance. I'm not too familiar with Objective-C, though. Is there a reason this isn't assigned with a @property setter? I'd love to submit a pull request if it should be changed, but if it's actually supposed to be this way, then I won't.

@lukeredpath
Copy link
Contributor

Hmm, on first glance I'm not sure what is causing this either.

The code is using ARC and the socket is being assigned to a strong instance variable.

I unfortunately do not have a Snow Leopard machine to test this on.

One theory is that when [socket close] is called in dealloc, it tries to notify its delegate (the PTPusherConnection instance) which has already been deallocced by that point. Maybe I should set the delegate to nil first.

@lukeredpath
Copy link
Contributor

Hmm, given its crashing in didConnect, my theory is unlikely.

@hamchapman
Copy link
Contributor

Closing as stale and seems like it was related to an old version os OS X.

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

No branches or pull requests

3 participants