There's exactly one instance per Chrome process, it serves tasks posted through base/task/thread_pool.h and as such you should rarely need to use the base::ThreadPoolInstance API directly (more on posting tasks later). In Chrome, this is base::ThreadPoolInstance. Thread pool: A pool of physical threads with a shared task queue.You should pretty much never be creating your own base::Thread's. base::Thread: A physical thread forever processing messages from a dedicated task queue until Quit().You should pretty much never use this directly.
The Chrome cross-platform abstraction is base::PlatformThread. pthread on POSIX or CreateThread() on Windows). Physical thread: An operating system provided thread (e.g.Task queue: A queue of tasks to be processed.In Chrome this is base::OnceCallback and base::RepeatingCallback created via base::BindOnce and base::BindRepeating, respectively. Effectively a function pointer with optionally associated state. This documentation assumes familiarity with computer science threading concepts. Absent external requirements about latency or workload, Chrome attempts to be a highly concurrent, but not necessarily parallel, system.Ī basic intro to the way Chromium does concurrency (especially Sequences) can be found here. Instead, objects live on only one (often virtual - we’ll get to that later!) thread and we pass messages between those threads for communication. We discourage locking and thread-safe objects. Our approach is to use message passing as the way of communicating between threads. This means offloading any blocking I/O or other expensive operations to other threads. “UI” thread in the browser process) and IO thread (each process‘s thread for receiving IPC) responsive. The main goal is to keep the main thread (a.k.a. In this document we will go over the basic threading system shared by each process. OverviewĬhrome has a multi-process architecture and each process is heavily multi-threaded. Note: See Threading and Tasks FAQ for more examples. SingleThreadTaskExecutor and TaskEnvironment.TaskRunner ownership (encourage no dependency injection).Adding additional work to a running job.Posting Tasks to a COM Single-Thread Apartment (STA) Thread (Windows).Posting to a Custom SingleThreadTaskRunner.Posting to the Main Thread in a Renderer Process.Posting to the Main Thread or to the IO Thread in the Browser Process.Posting Multiple Tasks to the Same Thread.Posting to the Current (Virtual) Thread.
0 kommentar(er)
