When Chrome Ate My RAM: Designing a Pressure-Aware Tab Orchestrator with Rust

Chrome wasn't "crashing." It was just...slowly suffocating my system. Over time, RAM usage would creep up. Background tabs accumulated state. Other applications started freezing. The fan would spin up. And yet, nothing looked obviously wrong. No single tab was the culprit. The problem wasn't too many tabs . The problem was a lack of coordination between the browser and the system. So I built something to experiment with that idea. This article explains the architecture and reasoning behind a hybrid Chrome extension & Rust native host that manages tab lifecycle based on real system pressure and user context. The Problem: Browser Entropy Modern browsers are operating systems. They manage: Dozens of isolated processes Background timers Network activity Memory-heavy applications (Jira, GitHub, Gmail, ChatGPT, Claude 😊 etc.) Most tab suspension tools rely on a simple rule: "If a tab hasn't been used in X minutes, suspend it." That's convenient, but blind. They don't know: Whether the system