Closed Bug 1652463 Opened 4 years ago Closed 3 years ago

Failed to create top level IPC between socket process and parent process on windows

Categories

(Core :: Security: Process Sandboxing, defect, P1)

Unspecified
Windows 10
defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox-esr91 --- fixed
firefox92 --- fixed
firefox93 --- fixed
firefox94 --- fixed

People

(Reporter: kershaw, Assigned: bobowen)

References

Details

Attachments

(1 obsolete file)

STR:

  1. set network.http.network_access_on_socket_process.enabled to true.
  2. Restrart firefox and access any https site.

Disabling sandbox by setting MOZ_DISABLE_SOCKET_PROCESS_SANDBOX=1 can fix this issue, so this should be related to sandboxing.

[Socket 12700, Socket Thread] WARNING: failed to create pipe: 5: file c:/work/mozilla-central/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 236
[Socket 12700, Socket Thread] WARNING: Unable to create pipe named "12700.0.728279352\355809996" in server mode.: file c:/work/mozilla-central/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 68
[Socket 12700, Socket Thread] WARNING: failed to create pipe: 2: file c:/work/mozilla-central/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 236

###!!! [Child][MessageChannel] Error: (msgtype=0x60056,name=PBackground::Msg_PVerifySSLServerCertConstructor) Channel error: cannot send/recv

Hit MOZ_CRASH(MsgDropped: Channel error: cannot send/recv) at c:/work/mozilla-central/ipc/glue/BackgroundChildImpl.cpp:153
[Parent 12336, Gecko_IOThread] ###!!! ABORT: file c:/work/mozilla-central/ipc/chromium/src/base/message_pump_win.cc, line 402
Assignee: nobody → bobowencode
Severity: -- → S4
Priority: -- → P1
Pushed by bobowencode@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/afc05ca167e7
Add rule to allow socket process to create server side of our IPC pipes. r=handyman
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla80

Backed out changeset afc05ca167e7 (Bug 1652463) for causing mochitest media spi failures.

Failures in test_peerConnection_asymmetricIsolation.html:
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=310706513&repo=autoland&lineNumber=4435

These have been tracked in Bug 1227386 and the increase in failures can be seen in
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?startday=2020-07-15&endday=2020-07-22&tree=trunk&bug=1227386

Backout by malexandru@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/33ebacea47a9
Backed out changeset afc05ca167e7 for causing mochitest media spi failures.
Status: RESOLVED → REOPENED
Flags: needinfo?(bobowencode)
Resolution: FIXED → ---
Target Milestone: mozilla80 → ---

kershaw - this caused bug 1227386 to become a perma-fail (see bug 1227386 comment 47 from bwc).

It seems unlikely that this change in itself would cause an issue.
The only thing I can think of is that something is now working that was blocked before, causing some sort of knock-on effect.

Flags: needinfo?(bobowencode) → needinfo?(kershaw)

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:bobowen, could you have a look please?
For more information, please visit auto_nag documentation.

Flags: needinfo?(bobowencode)

Waiting for information from :kershaw.

Flags: needinfo?(bobowencode)

It seems this test is no longer failed with this patch.
https://treeherder.mozilla.org/jobs?repo=try&revision=fb49873352221bc6b992bdc75a38c53c913e89de
Bug 1227386 also shows the last failure of this test was 4 months ago.

Bob, could you try to re-land this patch? Thanks.

Flags: needinfo?(kershaw) → needinfo?(bobowencode)

(In reply to Kershaw Chang [:kershaw] from comment #9)

It seems this test is no longer failed with this patch.
https://treeherder.mozilla.org/jobs?repo=try&revision=fb49873352221bc6b992bdc75a38c53c913e89de
Bug 1227386 also shows the last failure of this test was 4 months ago.

Bob, could you try to re-land this patch? Thanks.

Thanks for re-testing this, should be on autoland soon ...

Flags: needinfo?(bobowencode)
Status: REOPENED → RESOLVED
Closed: 4 years ago3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 93 Branch
Status: RESOLVED → REOPENED
Flags: needinfo?(bobowencode)
Resolution: FIXED → ---
Target Milestone: 93 Branch → ---

Turns out the work in bug 1713148 should have fixed this.

Status: REOPENED → RESOLVED
Closed: 3 years ago3 years ago
Depends on: 1713148
Flags: needinfo?(bobowencode)
Resolution: --- → FIXED
Attachment #9164381 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: