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

deadlocks #79

Open
emes opened this issue Dec 21, 2017 · 1 comment
Open

deadlocks #79

emes opened this issue Dec 21, 2017 · 1 comment

Comments

@emes
Copy link

emes commented Dec 21, 2017

We're seeing occasional deadlocks where jetfire is the only active thread. Any chance this starscream issue is also a jetfire issue? I'm guessing not.

daltoniam/Starscream#164 (comment)

@mistal-distal
Copy link

This usually comes down to application architecture, which I run into myself a lot. Was getting deadlocks until I read this part on the README.

By default dispatch_get_main_queue is used, thus making all delegate methods calls run on the main thread. It is important to note that all WebSocket processing is done on a background thread, only the delegate method calls are changed when modifying the queue. The actual processing is always on a background thread and will not pause your app.

It's very important to understand what thread model this (and other websocket libraries) run on.

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