Same here... crashes when there's video element with Blob/Base64 src value.. 

I will triage this tomorrow.

This is out of memory crash; the Netflix tab is consuming over 2GiB of memory.

This has been confirmed to only impact Dru? Or is this a wider issue?

I cannot reproduce this issue by playing 4K video on Youtube with multiple tabs, either on latest canary and the reported version, 11476.0.0.
Looking the report, Netflix tab consumes 2GB memory, and Youtube tab does 2GB too. It seems really awful.
Could you help me to know more what happens on your device, by providing me with the following info?
1.) chrome://media-internals log. There is "Save log" button.
2.) memory usage of GPU process and Browser process, and YouTube/Netflix tabs, immediately before crash happens.

Thank you very much in advance.

Pinged hsiangc@ for an update.

The issue no reproduce on M-73 build  11541.0.0/ 73.0.3664.0

Was there any code changes made from initial report of the issue and now? hiroh@ do you want to keep this bug open (but downgrade) for the consumption problem?

> Was there any code changes made from initial report of the issue and now?

I have no idea. I think there should have had some memory leakage (unrelated to video part, I guess) in the build and this was fixed now?

> hiroh@ do you want to keep this bug open (but downgrade) for the consumption problem?

I want to keep in my mind this until we find what fixed this issue.
cindyb@, do you know some person who tracks memory status in whole chrome/chromeos?

+ dianders@ listed as memory leaks POC. Can you help here?

Removing RBD and moving forward with dev. Investigation can continue.

I might not be the right POC for memory leaks these days.  There's a whole memory team who has been focused on helping with these situations and I haven't had time to keep up with their latest.  Sonny might be a good place to start?  Also Brian might be interested.

I'm not sure this is a system-level issue -- it seems like there's a leak in the Netflix site and since the site is focused, we won't kill that tab.  In the past there was someone in Chrome media who owned or dealt with Netflix issues, but I'm not sure who that would be.

I think memory leakage doesn't happen on GPU process.

> In the past there was someone in Chrome media who owned or dealt with Netflix issues, but I'm not sure who that would be.

+dalecurtis@, is anyone in media team in charge of memory issues?

Also +alberto -- said he had some Netflix contacts

I consider this is temporary Netflix side issue or general chrome issue, not GPU process side issue.
Let me close this and reopen again if the issue happens again.