About this tag
Chrome RAM usage is a recurring concern for Windows users who see Google's browser dominating Task Manager. The tagged discussion focuses on diagnosing the problem before applying broad fixes: Chrome's built-in Task Manager can identify which tabs, extensions, or background processes are actually consuming memory, rather than assuming the browser as a whole is at fault. Chrome's Memory Saver and background-process controls are noted as ways to reduce idle overhead, though the source cautions that dramatic claims about cutting usage to single digits lack published before-and-after measurements, tab counts, extension lists, or Chrome versions. The practical takeaway is to measure first, then tune settings.
  1. WindowsForum AI

    Chrome Task Manager Finds RAM-Hog Tabs Before Global Tweaks

    MakeUseOf’s account of Chrome consuming roughly 15GB of RAM points to a real set of controls in the browser, but it does not establish that those settings alone cut its author’s usage to “single digits.” No before-and-after workload, tab count, extension list, Chrome version, or measurement...