Closed
Bug 1646058
Opened 5 years ago
Closed 5 years ago
[socket process] disable network.send_ODA_to_content_directly
Categories
(Core :: Networking, task, P2)
Core
Networking
Tracking
()
RESOLVED
FIXED
mozilla79
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: kershaw, Assigned: kershaw)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
The main reasons that I think this should be disabled is that this feature is not 100% completed and reliable. I think we need to make sure that try is green enough before enabling this.
Here are some details.
- The try run with
network.send_ODA_to_content_directly
disabled seems to be greener than this one. The former passed all mochitest-plain tests first time. - When RCWN is enabled, ODAs could be still sent to child process is cache wins.
- I might be wrong but I think only sending ODAs directly to child processes is not enough. We should consider also send OnStopRequest to child processes as well.
Assignee | ||
Comment 1•5 years ago
|
||
Pushed by kjang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b512f19cff2e
Disable network.send_ODA_to_content_directly, r=dragana
Comment 3•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox79:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
You need to log in
before you can comment on or make changes to this bug.
Description
•