Isolation of networking process in a browser

Computer programs and applications are often designed such that sub-tasks of a program are executed by a separate process spawned by the main program or application. An advantage to such a design is resilience, e.g., even if one process fails, the remaining processes continue execution, even as the failed process is started anew. In the context of web browser applications, networking requests are typically not spawned as separate processes but rather handled by the main browser process itself. This can lead to problems of stability, security, and resilience. The techniques of this disclosure spawn the networking tasks of a web browser into a separate process, and can provide improved stability, security, and resilience