Closed
Bug 1393056
Opened 7 years ago
Closed 7 years ago
Count open WebSockets owned by an nsGlobalWindow
Categories
(Core :: DOM: Core & HTML, enhancement)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla57
Tracking | Status | |
---|---|---|
firefox57 | --- | fixed |
People
(Reporter: farre, Assigned: farre)
References
Details
Attachments
(1 file, 1 obsolete file)
5.41 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
To be able to not throttle timeouts in the TimeoutManager when there are active web sockets, we need to keep tabs on the amount of websockets opened, as well as closed.
Assignee | ||
Comment 1•7 years ago
|
||
Attachment #8900294 -
Flags: feedback?(bugs)
Comment 2•7 years ago
|
||
Comment on attachment 8900294 [details] [diff] [review] 0001-Bug-1393056-Make-it-possible-to-count-open-WebSocket.patch Shouldn't we count this per top level inner window, similar to IDB connection. We're supposed to throttle or not-throttle tabs after all, not some iframes in tabs, as far as I know.
Attachment #8900294 -
Flags: feedback?(bugs) → feedback-
Assignee | ||
Comment 3•7 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=c59c1c41a7726b3e6892022d890f8df680b695f4&group_state=expanded
Attachment #8900294 -
Attachment is obsolete: true
Attachment #8903194 -
Flags: review?(bugs)
Comment 4•7 years ago
|
||
Comment on attachment 8903194 [details] [diff] [review] 0001-Bug-1393056-Make-it-possible-to-count-open-WebSocket.patch In general, could you use -p -U 8 when generating patches.
Attachment #8903194 -
Flags: review?(bugs) → review+
Pushed by afarre@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/448006f5fb18 Make it possible to count open WebSockets on the main thread. r=smaug
Comment 6•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/448006f5fb18
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox57:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
Comment 7•6 years ago
|
||
Was the intention in this bug to avoid only budget based throttling of sites using websocket? It seems this bug did not prevent our normal 1second background throttle if the site is using websockets. Was this intentional?
Flags: needinfo?(afarre)
Assignee | ||
Comment 8•6 years ago
|
||
Yep, that was intentional. We're aligning with the behaviour of Chrome here in that we always, with the exception of audio, allow the 1s throttling.
Flags: needinfo?(afarre)
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•