Issue metadata
Sign in to add a comment
|
Memory.Gpu.PrivateMemoryFootprint is climbing on Mac |
||||||||||||||||||||||
Issue descriptionThis histogram has been climbing steadily since early September and is still climbing. I had expected a one-time jump during the MacViews launch, but the continuing growth on Stable is worrying.
,
Nov 26
+couple more GPU folks to have more eyes on this.
,
Nov 26
https://uma.googleplex.com/p/chrome/timeline_v2/?sid=c7280c6c32e4dc7c0ed83f75a3ada8d3 is the graph I'm looking at.
,
Nov 26
It's curious that while gpu has increased, the browser, renderer, and total memory have all decreased: https://uma.googleplex.com/p/chrome/timeline_v2/?sid=de8eeedca06d16058d7a0a71401cf52c I also checked out oop-raster (which was in finch on canary briefly) which moved memory from renderer to gpu, but that appears to make things better overall: https://uma.googleplex.com/p/chrome/timeline_v2/?sid=270af84f43d38832993dc402c753a6af
,
Nov 26
Is it possible to view this data normalized by the number of renderer processes? Could it be the case that users are on average leaving more tabs open, since the GPU process services all renderers?
,
Nov 27
I don't think you can do that, but Tabs.TabCount and Tabs.TabCountPerWindow are both flat on Mac: <https://uma.googleplex.com/p/chrome/timeline_v2/?sid=8b4c15c98946408923e279411636ea34> so I don't think the data we do have supports that hypothesis.
,
Nov 28
Thanks for the data. Guess we need another hypothesis.
,
Dec 10
For what it's worth, this metric is still climbing: the median is now at 165MB, up from 149MB a month ago and up from 159MB when I filed this.
,
Dec 11
,
Jan 2
This appears to have gone back down to a 147MB median over the last month. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kbr@chromium.org
, Nov 26