"ABORT: woke up from delay w/o being delayed" in mozilla::net::WebSocketChannel::Notify
Categories
(Core :: Networking: WebSockets, defect, P3)
Tracking
()
People
(Reporter: jruderman, Unassigned, NeedInfo)
References
Details
(Keywords: assertion, testcase, Whiteboard: [necko-backlog])
Attachments
(2 files)
Reporter | ||
Comment 1•11 years ago
|
||
Updated•9 years ago
|
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
I see the same happening that connecting to a websocket takes sometimes several seconds. This especially happens when I tried several reconnects that fails (triggers onerror), and suddenly the websocket is open again.
This not only a delay, but also a memory leak in FF. I'm using FF v75. Maybe this is not the correct bug id.
I see the same happening that connecting to a websocket takes sometimes several seconds. This especially happens when I tried several reconnects that fails (triggers onerror), and suddenly the websocket is open again.
I would like to add:
Basically the WebSocket in FF 1) is stuck in the "connecting state" after several failures of the websocket (when server was down). When the server is up again, then takes several seconds before the WS goes from the CONNECTING state to OPEN state in Firefox. Very strange.
The more retries I did before (causing onerror), the longer Firefox takes to go from connecting to open state, when there is actually a valid connection.
Comment 6•4 years ago
|
||
Hey Jesse,
Does this issue still reproduce for you or can we close it?
Comment 7•4 years ago
|
||
Marking this as Resolved > Incomplete as per reporter's lack of response.
If anyone can still reproduce this issue re-open it or file a new bug.
Description
•