User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce: * A simple python WebSocket server(example: https://github.com/dpallot/simple-websocket-server) * A simple client which retries to establish WebSocket connection on failure/close (example: https://gist.github.com/geethanjalieswaran/dc5a432a4f1e45df253eb1d29d76a73e) 1. start the python server 2. open/run the client on FF 3. stop the server for ~5 mins, but keep the client open 4. start the server and you can see a flood of stacked up WebSocket connections. Actual results: In Developer console-Network tab, you will see all the failed WebSocket connections are established again. We didn't observe this behavior on Chrome. We are noticing this behavior in past 6 months. Expected results: Apparently, only one WebSocket connection should have been established instead of all the stacked failed connections.
Assignee: nobody → michal.novotny
Bulk priority update: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
You need to log in before you can comment on or make changes to this bug.