I've been looking at sources of browser memory bloat by using native heap profiling on my own browser. Full details:
https://docs.google.com/document/d/1fN5balfyrd7sRpd6DRaUI1TwoOwYjLyRSd7mwZT5US8/edit#

Over the course of 1 week, the browser process created ~18k objects in AdsPageLoadMetricsObserver::OnDidFinishSubFrameNavigation() that it did not destroy. This is suggestive of a large leak.

Each screenshot shows:
  1) # of objects created [that have not been destroyed]
  2) The stack trace of the code that created the object.

jkarlin: Can you take a look?
 

Deleted: Screen Shot 2017-06-13 at 10.46.22 AM.png 288 KB

	Screen Shot 2017-06-13 at 10.46.22 AM.png 288 KB View Download