The Collapsed Memory Trap
Google Chrome introduced “Tab Groups” to help users organize massive amounts of open tabs by clustering them under color-coded labels. To save screen real estate, you can click a group’s label to “collapse” it, hiding all the tabs within. Behind the scenes, Chrome utilizes an experimental feature governed by the “Tab Groups Collapse Freezing” flag. When this flag is enabled, collapsing a tab group doesn’t just hide the tabs visually; it actively “freezes” them, suspending their execution in memory to save CPU cycles and RAM.
While freezing background tabs is generally a good thing for performance, tying it directly to the UI action of collapsing a group can be catastrophic for certain workflows. If you group together a series of active web applications—such as a live stock ticker, an active chat client (like Slack or Discord), or a page running a long data export—and then collapse the group to clear your screen, Chrome will instantly freeze them. Your chat will stop receiving messages, the stock ticker will halt, and the export will fail. If you use Tab Groups purely for visual organization and need the grouped tabs to continue processing data in the background even when hidden, you must disable this freezing behavior.
How to Stop Tab Groups from Freezing
You can force Chrome to keep tabs running normally even when they are hidden inside a collapsed group via the experimental flags menu.
- Open Google Chrome.
- Click inside the main address bar at the top of the browser window.
- Type
chrome://flagsand press Enter. - On the “Experiments” page, use the search bar to look for Tab Groups Collapse Freezing.
- If the flag is available, click the dropdown menu next to it and change it from “Default” (or Enabled) to Disabled.
- Click the blue Relaunch button at the bottom of the screen.
Upon restarting, collapsing a Tab Group will only change its visual state. The tabs hidden inside will continue to run, update, and consume resources exactly as they would if they were visible on the screen.