1474400 - Figure out how to make sure glyph caches aren't a problem for fission

Status: RESOLVED WORKSFORME

(Core :: Graphics, enhancement, P3)

Description

[Boris Zbarsky [:bzbarsky]]

We have bug 1258781 tracking some of the discussion around the skia glyph cache already, but we also have glyph caching going on in CoreText on Mac.   It's unclear to me so far (and to Lee, per email) whether DirectWrite does some sort of  caching itself.

In an ideal world, we would just have a single glyph cache, not a per-process one.  It sounds plausible that we might more or less get there with webrender, and then we can stop worrying about this as much.

Failing that, I'm not sure what options do we have here, apart from the things  already discussed in bug 1258781.

Comment 1

[Jeff Muizelaar [:jrmuizel]]

Yes, WebRender unifies the glyph cache into the gpu process. (I believe we currently have one cache per widget/window but we have plans to share that too)

Comment 2

[Anthony Jones (:ajones, :kentuckyfriedtakahe, :k17e)]

David - we're going to need to do some work here for fission if we don't get webrender.

Comment 3

[David Bolter [:davidb] (NeedInfo me for attention)]

Right. I was chatting with JeffM about this today. I think Lee and JKew will own the plan for our layer gfx stack and Lee is planning to attend the fission weekly tomorrow.

Comment 4

[Jeff Muizelaar [:jrmuizel]]

FWIW, Chrome currently has similar glyph cache problems so as long as our cache sizes are set similar it seems like this shouldn't block shipping. That being said, Chrome is getting out-of-process rasterization (you can turn it on now) which will give them a similar solution to WebRender.

Comment 5

[Lee Salzman [:lsalzman]]

It seems like we've gotten by just fine with lowering the glyph cache sizes. We can reopen this if further work is necessary later.