ChromeFlash
I built a Chrome extension to track where Chrome's RAM actually goes. Chrome uses a lot of memory. We all know this. But when I actually tried to figure out which tabs were eating my RAM, I realize...

Source: DEV Community
I built a Chrome extension to track where Chrome's RAM actually goes. Chrome uses a lot of memory. We all know this. But when I actually tried to figure out which tabs were eating my RAM, I realized Chrome doesn't make it easy. Task Manager gives you raw process IDs. chrome://memory-internals is a wall of text. Neither tells you "your 12 active tabs are using ~960 MB and your 2 YouTube tabs are using ~300 MB." So I built ChromeFlash — a Manifest V3 extension that estimates Chrome's memory by category and gives you tools to reclaim it. What it looks like The popup shows a breakdown of Chrome's estimated RAM: Browser Core — ~250 MB for Chrome's internal processes Active Tabs — ~80 MB each Pinned Tabs — ~50 MB each (lighter footprint) Media Tabs — ~150 MB each (audio/video) Suspended Tabs — ~1 MB each Extensions — estimated overhead A stacked color bar visualizes the proportions at a glance. The honest caveat Chrome's extension APIs in Manifest V3 don't expose per-tab memory. The chrome.p