Closed
Bug 1546355
Opened 6 years ago
Closed 6 years ago
[socket process] Try to launch socket process until we really need it
Categories
(Core :: Networking, enhancement, P2)
Core
Networking
Tracking
()
RESOLVED
FIXED
People
(Reporter: kershaw, Assigned: kershaw)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
Currently, socket process is launched before unit test started at [1].
This causes a problem that the socket process can't get prefs changes that made in test file, like [2]. The reason is that socket process is launched asynchronously and there is a race between updating prefs via IPC and launching the process.
Moreover, there are some tests that can't pass if we launch socket process, like bug 1513865. So, the best way could be launching the socket process until we make a first http request.
[1] https://hg.mozilla.org/projects/larch/file/tip/testing/xpcshell/head.js#l1488
[2] https://searchfox.org/mozilla-central/rev/f46e2bf881d522a440b30cbf5cf8d76fc212eaf4/netwerk/test/unit/test_content_length_underrun.js#34
|
Assignee | |
Comment 1•6 years ago
|
||
|
|
Assignee | |
Updated•6 years ago
|
Summary: [socket process] Try to launch socket porcess until we really need it → [socket process] Try to launch socket process until we really need it
|
||
Updated•6 years ago
|
Type: defect → enhancement
|
|
Assignee | |
Comment 2•6 years ago
|
||
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•