126599 2014-01-07 14:14:40 -0800 Web Inspector: AngularJS + SocketIO + Web Inspector = Locked Webpage 2014-03-24 09:07:24 -0700 1 1 1 Unclassified WebKit Web Inspector 528+ (Nightly build) Mac (Intel) OS X 10.9 RESOLVED FIXED InRadar P2 Major --- 1 cmoyer webkit-unassigned joepeck timothy webkit-bug-importer oldest_to_newest 965161 0 cmoyer 2014-01-07 14:14:40 -0800 I have an AngularJS application that creates several Socket.IO Connections back to a server, and as soon as I open the web inspector, the page freezes up, including the console, and becomes unresponsive. At this point I can't even close the tab, and have to force-close Webkit (the same happens with Safari, but I can close the tab there). 965162 1 webkit-bug-importer 2014-01-07 14:15:51 -0800 <rdar://problem/15766290> 965230 2 joepeck 2014-01-07 16:03:44 -0800 Chris, do you have a sample page or URL we can inspect to reproduce the issue? 965540 3 cmoyer 2014-01-08 10:26:18 -0800 I've gathered a few more details on the issue, and it's not quite what I thought before. I have disabled web sockets, and make Socket.IO use one of the other transports. I also noticed this ONLY happens over SSL. I've created a simple project to show the problem: https://github.com/kopertop/wkcrasher You don't even need to have it connect to socket.io on the backend, so I'm not sure if that is exactly the problem, but I know when I try to inspect this over SSL, the app (and inspector) completely hang up. 965569 4 timothy 2014-01-08 11:37:11 -0800 Thanks for creating a test case for us! 965571 5 cmoyer 2014-01-08 11:42:07 -0800 Digging a little further, if I comment out line 27 of js/services.js, the app works just fine, no crashes with the console opening up. So it looks like this only happens when I explicitly set the "transports" of socket.io: sockets[namespace] = io.connect(namespace, { transports: transports, // This line causes the problem 'connect timeout': 500, 'reconnect': true, 'reconnection delay': 500, 'reopen delay': 500, 'max reconnection attempts': 10 }); 993381 6 timothy 2014-03-21 16:53:55 -0700 Can you try your site in a recently nightly? 993822 7 cmoyer 2014-03-24 09:07:24 -0700 This appears to have fixed the problem. Thanks!