Add GlyphMetricsMap memory consumption to memory-infra tracing

[Not for Review] Add GlyphMetricsMap memory consumption to memory-infra tracing

Visiting Wikipedia and clicking through a set of pages on the same
domain, the glyphtoboundsmaps_total_size value climbs quickly to
1.2MB. This indicates removing the m_glyphsToBoundsMap might be a useful
area for saving memory.

BUG=589462
R=haraken,eae,tzik,kojii

[drott, 2016-07-06 11:38:34]

The CQ bit was checked by drott@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-07-06 11:38:51]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[drott, 2016-07-06 11:42:25]

Description was changed from

==========
Add GlyphMetricsMap memory consumption to memory-infra tracing

BUG=589462
R=haraken,eae,tzik,kojii
==========

to

==========
Add GlyphMetricsMap memory consumption to memory-infra tracing

Visiting Wikipedia and clicking through a set of pages on the same
domain, the glyphtoboundsmaps_total_size value climbs quickly to
1.2MB. This indicates removing the m_glyphsToBoundsMap might be a useful
area for saving memory.

BUG=589462
R=haraken,eae,tzik,kojii
==========

[drott, 2016-07-06 11:52:33]

Description was changed from

==========
Add GlyphMetricsMap memory consumption to memory-infra tracing

Visiting Wikipedia and clicking through a set of pages on the same
domain, the glyphtoboundsmaps_total_size value climbs quickly to
1.2MB. This indicates removing the m_glyphsToBoundsMap might be a useful
area for saving memory.

BUG=589462
R=haraken,eae,tzik,kojii
==========

to

==========
[Not for Review] Add GlyphMetricsMap memory consumption to memory-infra tracing

Visiting Wikipedia and clicking through a set of pages on the same
domain, the glyphtoboundsmaps_total_size value climbs quickly to
1.2MB. This indicates removing the m_glyphsToBoundsMap might be a useful
area for saving memory.

BUG=589462
R=haraken,eae,tzik,kojii
==========

[drott, 2016-07-06 11:52:33]

drott@chromium.org changed reviewers:
- eae@chromium.org, haraken@chromium.org, kojii@chromium.org, tzik@chromium.org

[drott, 2016-07-06 11:52:54]

Let's hold the review on this, I might remove the glyphtobounds map altogether.

[kojii, 2016-07-06 12:52:10]

On 2016/07/06 at 11:52:54, drott wrote:
> Let's hold the review on this, I might remove the glyphtobounds map
altogether.

I agree, this is cached in skia too if I recall our observation last time
correctly.

[drott, 2016-07-06 13:23:44]

On 2016/07/06 at 12:52:10, kojii wrote:
> On 2016/07/06 at 11:52:54, drott wrote:
> > Let's hold the review on this, I might remove the glyphtobounds map
altogether.
> 
> I agree, this is cached in skia too if I recall our observation last time
correctly.

Yes, since it seems to be quite significant in memory consumption, I am resuming
work on https://codereview.chromium.org/1980913002 - and if Mac cannot be
switched yet, we might have to #ifdef this, but I think we cannot do without
this memory saving on Android.

[commit-bot: I haz the power, 2016-07-06 13:37:38]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-07-06 13:37:39]

Dry run: This issue passed the CQ dry run.

[eae, 2016-07-06 16:10:18]

On 2016/07/06 11:52:54, drott wrote:
> Let's hold the review on this, I might remove the glyphtobounds map
altogether.

OK.

[drott, 2016-08-11 18:16:22]

Glyph metrics caches removed.