Bug 1577777 - perf-reftest-singletons (perf_reftest_singletons) harness should not alert on the overall number, just on the subtests Differential Revision: https://phabricator.services.mozilla.com/D53961 Differential Diff: PHID-DIFF-cvdbosopnqwdqbnmxiqz

Bug 1470591 - Part 7: Enable fork server by default.

Bug 1470591 - Part 6: Create a fork server process. r=gsvelto This patch make changes of Gecko infrastrutures to run a fork server process. - ForkServerLauncher is a component, which creates a fork server process at XPCOM startup. - nsBrowserApp.cpp and related files have been chagned to start a fork server in a process. - Logging and nsTraceRefcnt were changed to make it work with the fork server.

Bug 1470591 - Part 5: ForkServer to create new processes. r=gsvelto Class ForkServer and class ForkServiceChild are implemented. The chrome process can ask the fork server process to create content processes. The requests are sent by MiniTransceiver over a socket. The fork server replys with the process IDs/handles of created processes. LaunchOptions::use_forkserver is a boolean. With use_forkserver being true, the chrome process sends a request to the fork server instead of forking directly.

Bug 1470591 - Part 4: MiniTransceiver to do single-tasking IPC. r=gsvelto MiniTransceiver is a simple request-reponse transport, always waiting for a response from the server before sending next request. The requests are always initiated by the client.

Bug 1470591 - Part 3: AppForkBuilder to ceate a new content process. r=gsvelto An instance of AppForkBuilder creates a new content process from the passed args and LaunchOptions. It bascally does the same thing as LaunchApp() for Linux, but it divides the procedure to two parts, - the 1st part forking a new process, and - the 2nd part initializing FDs, ENV, and message loops. Going two parts gives fork servers a chance to clean new processes before the initialization and running WEB content. For example, to clean sensitive data from memory.

Bug 1470591 - Part 2: Provide methods to recreate a delegated forker. gsvelto With a fork server, the parameters to fork a new content process are passed through a socket. This patch does following tasks to adapt sandbox to work with a fork server, - passing a FD of a chroot server, - passing flags of SandboxFork, and - setting LaunchOptions and its fork_delegate field at a fork server.

Bug 1470591 - Part 1: Add a new process type for ForkServer. r=gsvelto

close

Bug 1470591 - Part 6: Create a fork server process. r=gsvelto This patch make changes of Gecko infrastrutures to run a fork server process. - ForkServerLauncher is a component, which creates a fork server process at XPCOM startup. - nsBrowserApp.cpp and related files have been chagned to start a fork server in a process. - Logging and nsTraceRefcnt were changed to make it work with the fork server.

Bug 1470591 - Part 5: ForkServer to create new processes. r=gsvelto Class ForkServer and class ForkServiceChild are implemented. The chrome process can ask the fork server process to create content processes. The requests are sent by MiniTransceiver over a socket. The fork server replys with the process IDs/handles of created processes. LaunchOptions::use_forkserver is a boolean. With use_forkserver being true, the chrome process sends a request to the fork server instead of forking directly.

Bug 1470591 - Part 4: MiniTransceiver to do single-tasking IPC. r=gsvelto MiniTransceiver is a simple request-reponse transport, always waiting for a response from the server before sending next request. The requests are always initiated by the client.

Bug 1470591 - Part 3: AppForkBuilder to ceate a new content process. r=gsvelto An instance of AppForkBuilder creates a new content process from the passed args and LaunchOptions. It bascally does the same thing as LaunchApp() for Linux, but it divides the procedure to two parts, - the 1st part forking a new process, and - the 2nd part initializing FDs, ENV, and message loops. Going two parts gives fork servers a chance to clean new processes before the initialization and running WEB content. For example, to clean sensitive data from memory.

Bug 1470591 - Part 2: Provide methods to recreate a delegated forker. gsvelto With a fork server, the parameters to fork a new content process are passed through a socket. This patch does following tasks to adapt sandbox to work with a fork server, - passing a FD of a chroot server, - passing flags of SandboxFork, and - setting LaunchOptions and its fork_delegate field at a fork server.

Bug 1470591 - Part 1: Add a new process type for ForkServer. r=gsvelto

close

Bug 1470591 - Part 1: Add a new process type for ForkServer. r=gsvelto Summary: Bug 1470591 - Part 2: Provide methods to recreate a delegated forker. r=gsvelto With a fork server, the parameters to fork a new content process are passed through a socket. This patch does following tasks to adapt sandbox to work with a fork server, - passing a FD of a chroot server, - passing flags of SandboxFork, and - setting LaunchOptions and its fork_delegate field at a fork server. Bug 1470591 - Part 3: AppForkBuilder to ceate a new content process. r=gsvelto An instance of AppForkBuilder creates a new content process from the passed args and LaunchOptions. It bascally does the same thing as LaunchApp() for Linux, but it divides the procedure to two parts, - the 1st part forking a new process, and - the 2nd part initializing FDs, ENV, and message loops. Going two parts gives fork servers a chance to clean new processes before the initialization and running WEB content. For example, to clean sensitive data from memory. Bug 1470591 - Part 4: MiniTransceiver to do single-tasking IPC. r=gsvelto MiniTransceiver is a simple request-reponse transport, always waiting for a response from the server before sending next request. The requests are always initiated by the client. Bug 1470591 - Part 5: ForkServer to create new processes. r=gsvelto Class ForkServer and class ForkServiceChild are implemented. The chrome process can ask the fork server process to create content processes. The requests are sent by MiniTransceiver over a socket. The fork server replys with the process IDs/handles of created processes. LaunchOptions::use_forkserver is a boolean. With use_forkserver being true, the chrome process sends a request to the fork server instead of forking directly. Bug 1470591 - Part 6: Create a fork server process. r=gsvelto This patch make changes of Gecko infrastrutures to run a fork server process. - ForkServerLauncher is a component, which creates a fork server process at XPCOM startup. - nsBrowserApp.cpp and related files have been chagned to start a fork server in a process. - Logging and nsTraceRefcnt were changed to make it work with the fork server. Tags: #secure-revision Differential Revision: https://phabricator.services.mozilla.com/D54391

Bug 1470591 - Part 5: ForkServer to create new processes. r=gsvelto Class ForkServer and class ForkServiceChild are implemented. The chrome process can ask the fork server process to create content processes. The requests are sent by MiniTransceiver over a socket. The fork server replys with the process IDs/handles of created processes. LaunchOptions::use_forkserver is a boolean. With use_forkserver being true, the chrome process sends a request to the fork server instead of forking directly.

Bug 1470591 - Part 4: MiniTransceiver to do single-tasking IPC. r=gsvelto MiniTransceiver is a simple request-reponse transport, always waiting for a response from the server before sending next request. The requests are always initiated by the client.

Bug 1470591 - Part 3: AppForkBuilder to ceate a new content process. r=gsvelto An instance of AppForkBuilder creates a new content process from the passed args and LaunchOptions. It bascally does the same thing as LaunchApp() for Linux, but it divides the procedure to two parts, - the 1st part forking a new process, and - the 2nd part initializing FDs, ENV, and message loops. Going two parts gives fork servers a chance to clean new processes before the initialization and running WEB content. For example, to clean sensitive data from memory.