← Back
Home › Systems › Operating systems and runtimes

browser-engine

web browser engine

Chromium, Gecko

SystemTechniques · 27Primitives · 65 browser-engine Generational garbage collectioncompilers · medium: Split the heap by age, collect the small young region often and cheaply, and rarely touch old data; wins whenever most objects die young.›Inline cachescompilers · medium: Per-call-site cache of "this object shape, that slot or target", turning dynamic property and method lookup into a compare and a load.›Javascript event loopcompilers · medium: Task and microtask queues, rendering steps, timers and promise job ordering in JS hostsDeterministic simulation testingdistributed · medium: Run the whole system in one thread under a seeded scheduler with simulated network, disk and clock, so every failure replays from its seed.›Primary-backup replicationdistributed · medium: One node orders all writes and ships them to standbys; the acknowledgement rule (none, one, all) sets what a crash loses, and an external arbiter decides who takes over.›Block inline layoutgraphics · medium: CSS box model: block formatting, inline formatting contexts, line boxes, floats and marginsCss cascade inheritancegraphics · medium: Resolve computed styles: origin and specificity ordering, inheritance, custom propertiesHidden classes (shapes)compilers · low: Objects that gained the same properties in the same order share one layout descriptor, so a property is an index and the layout is one comparable id.›Unicode line breakinggraphics · low: UAX 14 line break opportunities plus hyphenation hooksDamage trackinggraphics · low: Track dirty rectangles so each frame repaints and recomposites only what changedDisplay list recordinggraphics · low: Record draw commands into a replayable list for caching, culling and off-thread rasterHdr histogramdata-structures · low: Log-linear bucketed histograms with bounded relative error for latency percentilesProcess supervisionhardware-os · low: A parent process starts services, reaps their exits and restarts them under a delay and burst-limit policy, then stops them with SIGTERM before SIGKILL.›HTTP caching semanticsnetworking · low: The rules (RFC 9111) that decide whether a stored response is still fresh, and how a cheap conditional request revalidates it when it is not.›Mutual TLSsecurity · low: TLS where the client also proves a certificate key, so every connection carries a verified, rotatable machine identity.›Graceful drainingsystems · low: On a termination signal, stop taking new work, finish in-flight work until a deadline, tell clients to reconnect elsewhere, then exit; clients resume from a token.›Mark-sweep garbage collectioncompilers · low: Find everything reachable from the roots, free the rest in place; handles cycles, never moves objects, and is the base of most production collectors.›Dirty page trackinghardware-os · low: Write-protection or PML logs of modified guest/process pagesMachine code emissioncompilers · low: Encode instructions to bytes for x86-64 and AArch64, branch relaxation, constant poolsCooperative schedulingconcurrency · low: Green threads/coroutines yielding at await points on a user-space schedulerepoll event loopnetworking · low: One thread waits on thousands of non-blocking sockets with epoll_wait and handles only ready ones; the core of nginx, Redis and tokio.›Hierarchical timing wheelsystems · low: Timers bucketed by expiry into wheels of slots, coarser wheels for far deadlines: O(1) insert and cancel for millions of timeouts.›Record replaydistributed · low: Record every nondeterministic input (time, randomness, I/O, model and tool outputs, per-tick player input) and re-execute deterministically for debugging, replays and state rebuild+ 20 more techniques+ 49 more primitives

Similar systems

Share the most building blocks with this one.