If we have many tabs open, Chrome consumes a lot of memory -- it's hard to avoid this problem without having a smart TabManager & MemoryCoordinator (we're actively developing them now).

I might be more interested in cases where one tab is consuming  >1 GB of memory.

Metabugs need an owner. +chrisha as this  might have to do with tab killer.

TabManager is definitely aiming to address this, but the issues are broader than just what we're tackling (ie, there are thousand different things that could be contributing to the bloat). The TM work is mostly about treating the symptoms, but there's a lot of work that can be and is being done to also address underlying memory use problems. I'm not sure I make any more sense as a single owner?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I'll take this again as our team has been given a broader mandate of dealing with bloat when large numbers of tabs are in use. Ongoing discarding and lifecycles work should go a long ways towards addressing this.