The patch for this is out now. 👍

@vssummer That is quick! How can I get it? By this?
$ fetch --nohooks --no-history chromium
or by?
$ gclient runhooks

I can confirm that version 73.0.3657.0 does not demonstrate excessive RAM usage, as the total RAM usage stays consistently at ~ 400MB with all three tabs open (Wikipedia, Google, YouTube)

Thanks all of you for the infos. I'l do a new build and report back

Tried testing the issue on reported chromium version #73.0.3641.0 by using Ubuntu 17.10 following below steps.

Steps:
======
1.Launched chromium.
2.Navigated to "youtube.com","wikipedia.com" and "google.com".
3.Opened "system monitor" and observed that for each page an instance was formed.
4.Unable to see that 30% to 80% memory usage by chromium.

Attached screenshots for reference.
@reporter: Could you please review attached screenshots and let us know if anything is being missed from our end.
Thanks.!

Deleted: 918294.png 291 KB

	918294.png 291 KB View Download

Deleted: 918294_SystemDetails.png 55.8 KB

	918294_SystemDetails.png 55.8 KB View Download

@swarnasree.mukkala - main difference is that my Gnome is 3.30.2 with newer Gnome-shell and mutter (older versions suffered a memory leak)
I use "top" to monitor memory usage and after playing a few videos I see memory usage creeping up compared to begining session
Currently building newest version
[5427/22766] CXX obj/services/network/public/mojom/mojom_shared_cpp_sources/url_loader_factory.mojom-shared.o

Thank you for providing more feedback. Adding the requester to the cc list.

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

Tried testing the issue on reported chromium version #73.0.3641.0 using Ubuntu 17.10 Gnome 3.26.2 by following the steps as per comment #0. Observed that chromium does not use 30% to 80% memory usage and when killed the instances of chrome through system monitor observed that the memory got free.

Note: Tried installing and upgrading the Gnome 3.30.2 by using the following commands but could not upgrade.
sudo apt install gnome-session (install Gnome)
sudo apt-get update (update Gnome)
sudo apt-get dist-upgrade (update Gnome)

Attaching screenshots for reference.
@reporter: Could you please review attached screenshots and commands used to upgrade the Gnome, let us know if anything is being missed from our end.
Thanks.!

Deleted: System_Monitor.png 392 KB

	System_Monitor.png 392 KB View Download

Deleted: System_Details.png 80.2 KB

	System_Details.png 80.2 KB View Download

@swarnasree.mukkala
My system is LFS where Gnome is very up-to-date. The reason I use the newest Gnome is that there is some strange interaction in Gnome and Chromium: Opening Chromium and Evolution and swiching focus repeatedly between those two with many right-clicks are causing Chromium to crash and sometimes crashing Xwayland too. I haven't reported that bug because I haven't discovered where the bug is located

Thank you for providing more feedback. Adding the requester to the cc list.

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

As per comment#7, it seems that the issue is related to Gnome 3.30.2 which is currently not present with TE to triage the issue. Unable to reproduce the issue with the setup present with us. Hence requesting someone from the dev team to look into the issue and help us in further triaging. Adding Stability-Memory label.

Thanks.!

@comment#12
Just built 73.0.3658.0. But I still suspect memory usage:
1. starting PC and login. Mem usage 31.6%
2. start and close chromium. Mem 32.2%
3. again. Mem 32.3%
4. again. with reloading start page a few times. Mem 37.3%
5, just start and close chromium. Mem. 37.5%
6. start chromium and openig wikipedia pages in multiple tabs then closing chromium. Mem 43.7%

Addition to Comment#13
Tested a few other gtk+apps and they leave behind a 0.05-0.2% footprint in memory. I believe now a Gnome-3.30.2 issue. It could only be dicovered by using Chromium because it uses many PIDS

As per comment#14, the issue seems to be specific to Gnome-3.30.2, hence adding TE-NeedsTriageHelp label and requesting the respective team to look into the issue.

Thanks.!