Crash on Safari when using WebSockets

[davidfowl]

Likely related to #2743 #2650. I've been using JabbR on Safari for a while now and I see the following crash every now and then. Likely a Safari bug but putting this here regardless

0   com.apple.WebCore               0x0000000109c49fd9 WebCore::SocketStreamHandleBase::close() + 9
1   com.apple.WebCore               0x0000000109d6f292 WebCore::WebSocketChannel::processOutgoingFrameQueue() + 786
2   com.apple.WebCore               0x0000000109d71ee6 WebCore::WebSocketChannel::processFrame() + 4838
3   com.apple.WebCore               0x0000000109d704e5 WebCore::WebSocketChannel::processBuffer() + 117
4   com.apple.WebCore               0x0000000109d7044c WebCore::WebSocketChannel::didReceiveSocketStreamData(WebCore::SocketStreamHandle*, char const*, int) + 364
5   com.apple.WebCore               0x0000000109c4bced WebCore::SocketStreamHandle::readStreamCallback(unsigned long) + 365
6   com.apple.CoreFoundation        0x00007fff8e3b2c81 _signalEventSync + 385
7   com.apple.CoreFoundation        0x00007fff8e3b2ac8 _cfstream_solo_signalEventSync + 328
8   com.apple.CoreFoundation        0x00007fff8e3b293f _CFStreamSignalEvent + 623
9   com.apple.CFNetwork             0x00007fff8d5f801a CoreReadStreamCFStreamSupport::coreStreamReadEvent(__CoreReadStream*, unsigned long) + 102
10  com.apple.CFNetwork             0x00007fff8d5f7f89 CoreReadStreamClient::coreStreamEventsAvailable(unsigned long) + 53
11  com.apple.CFNetwork             0x00007fff8d72ba65 CoreStreamBase::_callClientNow(CoreStreamClient*) + 53
12  com.apple.CFNetwork             0x00007fff8d5f7ca9 CoreStreamBase::_streamSetEventAndScheduleDelivery(unsigned long, unsigned char) + 183
13  com.apple.CFNetwork             0x00007fff8d5f7a32 SocketStream::dispatchSignalFromSocketCallbackUnlocked(SocketStreamSignalHolder*) + 74
14  com.apple.CFNetwork             0x00007fff8d5f7160 SocketStream::socketCallback(__CFSocket*, unsigned long, __CFData const*, void const*) + 206
15  com.apple.CFNetwork             0x00007fff8d5f7062 SocketStream::_SocketCallBack_stream(__CFSocket*, unsigned long, __CFData const*, void const*, void*) + 64
16  com.apple.CoreFoundation        0x00007fff8e3b2107 __CFSocketPerformV0 + 855
17  com.apple.CoreFoundation        0x00007fff8e372661 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
18  com.apple.CoreFoundation        0x00007fff8e363d12 __CFRunLoopDoSources0 + 242
19  com.apple.CoreFoundation        0x00007fff8e36349f __CFRunLoopRun + 831
20  com.apple.CoreFoundation        0x00007fff8e362f25 CFRunLoopRunSpecific + 309
21  com.apple.HIToolbox             0x00007fff8c424a0d RunCurrentEventLoopInMode + 226
22  com.apple.HIToolbox             0x00007fff8c4247b7 ReceiveNextEventCommon + 479
23  com.apple.HIToolbox             0x00007fff8c4245bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
24  com.apple.AppKit                0x00007fff8c71826e _DPSNextEvent + 1434
25  com.apple.AppKit                0x00007fff8c7178bb -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
26  com.apple.AppKit                0x00007fff8c70b9bc -[NSApplication run] + 553
27  com.apple.AppKit                0x00007fff8c6f67a3 NSApplicationMain + 940
28  com.apple.XPCService            0x00007fff864d7c0f _xpc_main + 385
29  libxpc.dylib                    0x00007fff8d27ebde xpc_main + 399
30  com.apple.WebKit.WebContent     0x0000000108834ba0 0x108834000 + 2976
31  libdyld.dylib                   0x00007fff859105fd start + 1

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib          0x00007fff83dbc662 kevent64 + 10
1   libdispatch.dylib               0x00007fff8ffb0421 _dispatch_mgr_invoke + 239
2   libdispatch.dylib               0x00007fff8ffb0136 _dispatch_mgr_thread + 52
...

[last-Programmer]

We are also getting this error in yosemite 10.10.1, Safari 8 crashes now and then

[aspnet-hello]

This issue has been closed as part of issue clean-up as described in https://blogs.msdn.microsoft.com/webdev/2018/09/17/the-future-of-asp-net-signalr/. If you're still encountering this problem, please feel free to re-open and comment to let us know! We're still interested in hearing from you, the backlog just got a little big and we had to do a bulk clean up to get back on top of things. Thanks for your continued feedback!