Google is rolling out a November update for its new Googlebooks that reclaims up to 6GB of RAM — not by making Chrome leaner, but by throttling the on-device AI services that were hogging your memory in the first place. The bottom line for users: Google's browser got so bloated it was crashing your laptop, and the fix is just robbing one Google process to feed another.
Android Police reported that the update "optimizes on-device AI services, enabling the OS to reclaim more system memory when Chrome requires more memory to run smoothly." That's a remarkable admission dressed up as a feature. Chrome — the gateway through which Google harvests browsing data, serves ads, and tracks users across the web — had become so resource-hungry that the operating system had to yank memory away from other tasks just to keep it from collapsing.
9to5Google, which cataloged 31 fixes in the update, was more clinical: "Improved memory usage for on-device AI, improving multitasking stability on 16GB devices." Buried in that passive language is the real story. These laptops ship with 16GB of RAM, and Google's AI and browser code were consuming enough of it to destabilize the machine. The November update updates the NPU driver's memory management on the Acer Googlebook 14, Asus Googlebook 14, and Lenovo Googlebook 15, freeing up 3–6GB of RAM, according to Android Police. That's up to a third of the total memory on these machines — eaten by Google's own processes before you ever open a single tab.
Both outlets frame this as good news. Neither asks the obvious question: why does a browser need the operating system to forcibly reallocate gigabytes of memory just to function? The answer is that Chrome hasn't been a simple browser for years. It's a data-collection platform, an ad-delivery engine, and now an AI inference pipeline — all running on your hardware, consuming your resources, for Google's benefit.
The rest of the update is a laundry list of what should have worked at launch. Bluetooth audio had lip-sync lag with wireless earbuds. External monitors showed black screens during Netflix playback. The Linux Terminal beta dropped SSH connections and killed virtual machines when you closed a window. Keystrokes didn't register on the lock screen. Display drivers crashed when you unplugged a USB-C hub. These are basic functions on a laptop, and Google shipped a product that couldn't do them reliably.
9to5Google noted that the HP and Dell XPS models received the most fixes — eight and nine respectively — suggesting the hardware that reviewers likely tested was the most broken. Android Police, meanwhile, framed the entire rollout as Google being "hard at work on improving the experience for early adopters" — a generous way of saying paying customers got a beta product.
Every Google update that adds AI features, telemetry hooks, or background data processes costs you RAM, battery life, and processor cycles. The November Googlebook update doesn't fix that architecture. It just manages the symptoms. Next month, when Google adds more on-device AI features, expect the cycle to repeat — and expect your hardware to foot the bill.
