You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you reproduce this issue with the current release?
Yes
Can you reproduce this issue with the beta channel?
Untested
Can you reproduce this issue with the nightly channel?
Untested
Other Additional Information:
Does the issue resolve itself when disabling Brave Shields?
No
Does the issue resolve itself when disabling Brave Rewards?
No
Is the issue reproducible on the latest version of Chrome?
No
Miscellaneous Information:
This issue is persistent on browser tab close.
I had attempted explicitly closing the websocket through registering a window.unload event handler, and this still didn't resolve the issue.
window.addEventListener("unload",function(){// Also tested with != Websocket.CLOSEDif(COMMAND_SOCKET.readyState==WebSocket.OPEN)COMMAND_SOCKET.close();});
This appears to already be resolved in Chrome, Opera, and FF.
The text was updated successfully, but these errors were encountered:
Yes it is categorized wrong. I don't understand why that has been labeled as repros-on-chrome & Chromium/waiting upstream. It was labeled by rebron because he thought it relates to some chromium issue. After that OP said it doesn't repro on Chrome #15410 (comment) but rebron didn't remove the label.
Description
Websockets are sometimes not cleanly terminated on
window.unload
, even if a specific event handler is registered toclose()
the websocket.Steps to Reproduce
CTRL+R
as fast as you canKeep-Alive
timeout, causing WS from new tab loads to not connect.Actual result:
WS can remain open on
window.unload
, even when explicitly closing it.Expected result:
All websockets should cleanly terminate on browser unload.
Reproduces how often:
Easily reproduced.
Brave version (brave://version info)
Brave | 1.31.87 Chromium: 95.0.4638.54 (Official Build) (64-bit)
Revision | d31a821ec901f68d0d34ccdbaea45b4c86ce543e-refs/branch-heads/4638@{# 871}
Version/Channel Information:
Yes
Untested
Untested
Other Additional Information:
No
No
No
Miscellaneous Information:
This issue is persistent on browser tab close.
I had attempted explicitly closing the websocket through registering a
window.unload
event handler, and this still didn't resolve the issue.This appears to already be resolved in Chrome, Opera, and FF.
The text was updated successfully, but these errors were encountered: