Steps to reproduce the problem:
1. Open more than 100 tabs (so that the counter displays ";)" instead of an actual number.
2. Scroll quickly through the tabs by swiping up the whole way. Delete a few tabs quickly if not yet crashed.
3. Observe brief hang, and then app crash.

What is the expected behavior?
Chrome should use memory gracefully when scrolling through tabs, like it does when I swipe left and right. Maybe Chrome shouldn't re-render pages when memory pressure is high?

What went wrong?
Unlike switching tabs by swiping the URL bar, scrolling through the tabs is significantly more likely to cause an OOM. I can swipe left and right through every tab without any issue whatsoever.

If you've opened more than 100 tabs, this makes it extremely hard to actually close tabs without losing ALL of the open tabs.

It might have something to do with rendering tab contents. I think Chrome reloads individual tab contents while scrolling, and maybe it's not releasing them quickly enough? Maybe it's not releasing them when they're out of view?

Crashed report ID: 606ad29e00000000

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? No 

Chrome version: 54.0.2840.25  Channel: beta
OS Version: 7.0
Flash Version: 

I've seen lots of effort at handling high memory pressure conditions in the chromium codebase - there's some very impressive work in chromium!