You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i had this issue when trying to close sockets on "pause" event. the first one would close, but the other would get stuck in CLOSING, with no way to get it out of that state. I tried the following ugliness when trying to reopen the socket:
// nasty kludge -- should look to see
// if we can use chrome.sockets.tcp instead .. . .
if (this.socket.state = Socket.State.CLOSING) {
this.socket._state = Socket.State.CLOSED;
}
and it seemed to work, but of course, it created all sorts of havok. anyone have any ideas on this?
Running this on iOS my socket frequently gets stuck in the CLOSING state. Is there any way to destructively close a socket.
The text was updated successfully, but these errors were encountered: