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

SIGABRT in TMReachabilityCallback #167

Open
Sega-Zero opened this issue Mar 26, 2018 · 1 comment
Open

SIGABRT in TMReachabilityCallback #167

Sega-Zero opened this issue Mar 26, 2018 · 1 comment

Comments

@Sega-Zero
Copy link

Using Reachability via Cocoapods in swift project. Sometimes catching a crash like this:
reachability m 2018-03-26 20-18-11

Cannot reproduce this crash, but I catch it on device only.
Could it happen because I call stopNotifier in instance owner deinit?

Probably, the object has been already deallocated, but a block in reachabilitySerialQueue is still executed. Wouldn't it be better to pass self in context.info using __bridge_retained so no garbage will pass in the callback?

@chrisballinger
Copy link

We are also seeing this crash. Changing to __bridge_retained and __bridge_transfer introduced even more crashes.

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

2 participants