Safari (Mac Only) crashes when using websocket

[pbcomm]

I am using the very basic example listed on the website, not sending or receiving any messages, just connecting.
Connection is on 127.0.0.1:80
On connect Safari crashes with following:

Process: Safari [11081]
Path: /Applications/Safari.app/Contents/MacOS/Safari
Identifier: com.apple.Safari
Version: 5.0.5 (6533.21.1)
Build Info: WebBrowser-75332101~1
Code Type: X86-64 (Native)
Parent Process: launchd [238]

Date/Time: 2011-04-23 02:40:30.463 -0400
OS Version: Mac OS X 10.6.7 (10J869)
Report Version: 6

Interval Since Last Report: 140807 sec
Crashes Since Last Report: 20
Per-App Interval Since Last Report: 36857 sec
Per-App Crashes Since Last Report: 16
Anonymous UUID: 545FB01F-FF2E-4A16-9EFC-A8A538906A53

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x00007fff87e11c00 CFArrayGetCount + 80
1 com.apple.WebCore 0x00007fff82a3150b WebCore::SocketStreamHandle::chooseProxyFromArray(CFArray const) + 43
2 com.apple.WebCore 0x00007fff82cc6088 WebCore::SocketStreamHandle::pacExecutionCallbackMainThread(void) + 24
3 com.apple.JavaScriptCore 0x00007fff87bf6848 WTF::callOnMainThreadAndWait(void ()(void), void_) + 72
4 com.apple.WebCore 0x00007fff82cc5ec0 WebCore::SocketStreamHandle::pacExecutionCallback(void_, _CFArray const, _CFError) + 32
5 com.apple.CFNetwork 0x00007fff86cd167c executionContextPerform(void*) + 1079
6 com.apple.CoreFoundation 0x00007fff87e4f401 __CFRunLoopDoSources0 + 1361
7 com.apple.CoreFoundation 0x00007fff87e4d5f9 __CFRunLoopRun + 873
8 com.apple.CoreFoundation 0x00007fff87e4cdbf CFRunLoopRunSpecific + 575
9 com.apple.HIToolbox 0x00007fff830237ee RunCurrentEventLoopInMode + 333
10 com.apple.HIToolbox 0x00007fff83023551 ReceiveNextEventCommon + 148
11 com.apple.HIToolbox 0x00007fff830234ac BlockUntilNextEventMatchingListInMode + 59
12 com.apple.AppKit 0x00007fff80441e64 _DPSNextEvent + 718
13 com.apple.AppKit 0x00007fff804417a9 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155
14 com.apple.Safari 0x0000000100015ff6 0x100000000 + 90102
15 com.apple.AppKit 0x00007fff8040748b -[NSApplication run] + 395
16 com.apple.AppKit 0x00007fff804001a8 NSApplicationMain + 364
17 com.apple.Safari 0x0000000100009f18 0x100000000 + 40728

[3rd-Eden]

Known issue, it's a bug in safari. I have already reported it and the apple engineers are working on it. To solve it, turn off auto proxy discovery in your network settings

[3rd-Eden]

Small note: it's not a bug caused by socket.io, as every web socket connection will crash and there is no way to detect this.

[pbcomm]

Haha, I have just discovered the same thing, however I though it's my companies proxy that was the issue. I guess it's all of them. Interesting that it only happens on mac.
Thank you.

[3rd-Eden]

One last note, just for the sake of completion: The bug can be found in Apples bugbase under Bug ID# 8244376. This bug is not present in the latest Webkit builds or in google chrome. So if you have suffer from this bug, and can't disable the Auto Proxy Discovery option you can use those browsers instead :)

[dvv]

This issue is true for Safari for Windows too. Please, update the issue title.

[NuckChorris]

Also happening on Safari Mobile over 3G, I'm assuming that acts as a proxy.

[3rd-Eden]

What IOS version are you running? Also which phone ? Iphone 1, 3gs, 4 or 5 ;)?

On 4 sep. 2011, at 02:05, NuckChorris wrote:

Also happening on Safari Mobile over 3G, I'm assuming that acts as a proxy.

Reply to this email directly or view it on GitHub:
#193 (comment)

[NuckChorris]

iOS 4.3.5 on an iPhone 4 GSM

[CameronJ]

I just noticed the same problem on iOS 5.1 (iPhone 4S). So I assume that Apple still has not fixed this one.

After the page goes to the background (app hidden) or tab changes. Returning to the tab causes safari to crash.

[christopherobin]

It's also the case on iOS 5.0 (iPad 2) using a Manual Proxy. As soon as the websocket is created Safari just crash.

[NuckChorris]

Perhaps it'd be smart to add a workaround in the meantime, by detecting iOS Safari and preventing WebSockets on there, just falling back to the other transports?

On Dec 6, 2011, at 11:35 PM, Christophe Robinreply@reply.github.com wrote:

It's also the case on iOS 5.0 (iPad 2) using a Manual Proxy. As soon as the websocket is created Safari just crash.

---

Reply to this email directly or view it on GitHub:
#193 (comment)

[NuckChorris]

I think this issue needs to be reopened, since it's quite clearly a major issue that isn't getting solved any time soon, it needs a workaround patch.

[3rd-Eden]

@NuckChorris The only possible work around is to disable WebSockets for every safari, ever. And that is not viable. There are no workarounds for this issue as it's not detectable.

@guille opinions?

[NuckChorris]

I think this is a serious issue that deserves even the ugliest of hacks (like sniffing the UA string for browser version)

Crashing any browsers is just unacceptable behavior.