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
EXC_BAD_ACCESS in closeWithCode #314
Comments
Same thing is happening with my code. Could somebody please help in debugging the issue. |
Any chance you can post a full stack trace? |
Here is the link to crash on fabric http://crashes.to/s/4e4411184da On Tue, Jun 21, 2016 at 11:00 PM, Nikita Lutsenko notifications@github.com
Rohan Gupta |
@rohg, ok, this is helpful... Any chance you can specify the commit from SocketRocket that you are using? I am trying to find the exact line where it crashes right now. |
I'm having the same crash. It isn't easily reproducible, but I managed to capture it in Xcode a few mins ago: This was captured from SocketRocket version 0.5.0 . Here's the backtrace of all threads (some stack frames from the main thread elided for privacy reasons):
|
Woo, that helps even more! |
@erikprice, can you also share some context from |
Also, are you guys using KVO for |
Whee! I got to the same stack trace! Debugging and doing some extreme load things to reproduce and then validate. |
Yes, we are KVO'ing the
|
I got it to crash consistently now, which is a good start! |
@erikprice @NVentimiglia @rohg, just pushed an update to #420 that makes readyState fully thread safe and properly KV Observable. |
Will do that now. Thanks for the quick turnaround, @nlutsenko . |
@nlutsenko Thank you for prompt help. I will check and will update if any issue. |
I am attempting to connect to a web socket using this library from within a Unity3d application. Shortly after calling Open I get a crash with a EXC_BAD_ACCESS (code=1, address=0x30) on thread 1. I am not sure how to debug this. Here is the code that Xcode shows me.
I am crashing on the dispatch_async line.
my code is below
Am I doing it wrong ?
The text was updated successfully, but these errors were encountered: