Failed to create top level IPC between socket process and parent process on windows
Categories
(Core :: Security: Process Sandboxing, defect, P1)
Tracking
()
People
(Reporter: kershaw, Assigned: bobowen)
References
Details
Attachments
(1 obsolete file)
STR:
- set
network.http.network_access_on_socket_process.enabled
to true. - 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
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Comment 3•5 years ago
|
||
bugherder |
Comment 4•5 years ago
|
||
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
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
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.
Comment 7•4 years ago
|
||
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.
Assignee | ||
Comment 8•4 years ago
|
||
Waiting for information from :kershaw.
Reporter | ||
Comment 9•3 years ago
|
||
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.
Assignee | ||
Comment 10•3 years ago
|
||
(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 ...
Comment 11•3 years ago
|
||
bugherder |
Comment 12•3 years ago
|
||
Backed out as per request.
Comment 13•3 years ago
|
||
Backout go merged to central: https://hg.mozilla.org/mozilla-central/rev/57aa1b41c49b
Comment hidden (obsolete) |
Assignee | ||
Comment 15•3 years ago
|
||
Turns out the work in bug 1713148 should have fixed this.
Updated•3 years ago
|
Description
•