Web pages have memory leaks, not Chrome itself. Side note, but at least on linux, with both Chromium and Firefox, you can observe exactly this behavior- tab-ba

Web pages have memory leaks, not Chrome itself. Side note, but at least on linux, with both Chromium and Firefox, you can observe exactly this behavior- tab-based segregated memory management. The work was done on both engines over the past several years, works beautifully now. The content of each tab lives in a separate process. Kill the process, see the tab marked failed in the UI. Reload the tab, see a corresponding process spin back up. I keep dozens of tabs open and periodically kill the ones that creep to the top of ram use, both wired ram and virtual. Keeps me from going into swap.