-
Notifications
You must be signed in to change notification settings - Fork 3k
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
KERN_INVALID_ADDRESS crash in [currentRunLoop runMode] #541
Comments
Fix RunLoop / performSelector crash #541
I'm also getting same crash, waiting for any fix/progress, thanks @chrisballinger , does this commit fix the issue?
|
This issue has been marked as stale, it will be closed automatically if there is no further activity. |
I have encountered the same problem. May I ask how this problem was resolved later |
I just ported my application to CocoaAsyncSocket, and now my number 1 crashing bug is one in
CocoaAsyncSocket: GCDAsyncSocket-CFStream
Here is the thread
I also can see that I have 2 other threads running the following code:
and
The crashing line is in this static method:
and is specifically this line:
[currentRunLoop runMode:NSDefaultRunLoopMode beforeDate:[NSDate distantFuture]
Can anyone suggest why this method could be triggering an invalid
nil
address exception inCocoaAsyncSocket
?Thanks!
The text was updated successfully, but these errors were encountered: