Closed Bug 1646058 Opened 3 months ago Closed 3 months ago

[socket process] disable network.send_ODA_to_content_directly

Categories

(Core :: Networking, task, P2)

task

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.

  1. 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.
  2. When RCWN is enabled, ODAs could be still sent to child process is cache wins.
  3. 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.
Pushed by kjang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b512f19cff2e
Disable network.send_ODA_to_content_directly, r=dragana
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
You need to log in before you can comment on or make changes to this bug.