When using signalR in IE, if the browser is closed the streaming connection does not go away. It just sit there and hog memory.
That's nothing to do with SignalR. We hold onto connections until the webserver tells us it is gone. Does it stay forever? Hours? minutes? It's definitely not immediate after closing the browser but it does time out.
I did not count how long it stayed open. But one will assume that if there a connection streaming data, then closing the browser that is using the stream will automatically close the connection since the browser is no longer open. The problem also occurs when the page is refreshed. If it is done enough time(2 times), due to the limitation set by the browser no new connection would be made and would make signalR not work.
I think a good solution for this is to make a call to the server onbeforeunload and let that call close the connection that is streaming the messages.
I've made some changes to do this. It's a best effort /abort request that attempts to kill the other connection.
Dupe of #396