Closed
Bug 607924
Opened 14 years ago
Closed 11 years ago
e10s: turn off socket transport thread in child
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: jduell.mcbugs, Unassigned)
References
Details
(Whiteboard: [MemShrink:P3])
Followup from bug 559714. We want to turn off the socket transport thread in the child if nothing is using it. It's not a big win (just removes idle thread), but is the Right Thing to do. Bug 559714 comment 28 says "Turning off the socket transport is a nonstarter since it's needed by nsServerSocket which is created by httpd.js which is launched in child netwerk xpcshell tests." If this is true I'm not sure how xpcshell tests are working on Android--I thought child processes couldn't open TCP sockets there. Anyway, let's look into this and fix is possible.
Reporter | ||
Comment 1•14 years ago
|
||
Note: patch to turn off thread is available in bug 559714.
Reporter | ||
Comment 2•12 years ago
|
||
So this appears to be blocked because necko xpcshell tests need to use the socket transports to run httpd.js (see 559714 comment 28). We could presumably fix that by changing the IPC xpcshell tests to launch httpd.js in the parent instead of the child.
Updated•11 years ago
|
Whiteboard: [MemShrink]
Updated•11 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P3]
Reporter | ||
Comment 4•11 years ago
|
||
:ekr tells me webRTC is using the socket transport in child processes.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•