1192773 - Connection to websocket service takes longer and longer as more tabs are opened with the same connection, if server is closed while these connections where opened.

Status: UNCONFIRMED

(Core :: Networking: WebSockets, defect, P3)

Description

[uaalto]

Attachment: wstest.zip

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 Firefox/39.0
Build ID: 20150630154324

Steps to reproduce:

In order to reproduce this bug you need to follow these steps:

1) Run a service such as the attached Node websockets test server, on localhost.
2) Open a web page that connects to this websockets service. Make sure that the page connects to it. In the provided example, you need to click 'connect'.
3) Do this with at least 5 more tabs, but 10-12 is recommended to see clearer results.
3) Now kill the server.
4) The pages should now show 'not connected'.
5) Run the server again.
6) Click connect in ALL pages.

Can be reproduced at least on OSX and Windows.


Actual results:

Beyond the 4-5 pages threshold, it takes more and more time to initiate this connection. This builds up waiting time with each extra connection that you have established: the more pages you have, the more it takes to connect.

Additionally, this blocking behavior affects all tabs, but as soon as one connects, all of them do.


Expected results:

Pages should try to connect instantly, as soon as connection is requested. On Chrome, Safari and IE, that is what happens.

Comment 1

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 2

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258