[Bug 1930700] Re: Firefox 89 won't load pages due to many fonts

Bug Watch Updater 1930700 at bugs.launchpad.net
Mon Jun 21 09:11:23 UTC 2021

Launchpad has imported 13 comments from the remote bug at

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at

On 2021-02-22T15:49:49+00:00 Jfkthame wrote:

Currently gfx.e10s.font-list.shared is enabled by default on
Nightly/early Beta, but disabled for release.

To reduce content-process memory footprint and startup time, we should
get this enabled all the way to the Release channel.

Reply at:

On 2021-02-24T20:29:38+00:00 Cpeterson-3 wrote:

How much memory does the shared font-list save per content process?

Since Fission will have launch many more content processes than e10s,
the shared font-list might be nice to have for Fission MVP.

Reply at:

On 2021-03-01T20:08:21+00:00 Cpeterson-3 wrote:

@ Jonathan, SearchAllFontsForChar crash bug 1667977 and src:local() bug
1694123 are blocking this bug. I see you already have a patch up to fix
bug 1694123. Does bug 1667977 also need to be fixed before we can let
the shared font-list ride the trains to late Beta and Release?

Fission's current perf measurements are all from Nightly, so already
include any perf and memory benefits from the shared font-list. Tracking
for Fission M7 Beta milestone because we'd like to have the shared font-
list in late Beta and when we ship to Release.

kmag estimates the shared font-list might save about 500 KB in each
content process.

Reply at:

On 2021-03-02T09:13:58+00:00 Jfkthame wrote:

Bug 1667977 currently means that on Windows there's a possibility of
content processes crashing if the user installs/removes a bunch of fonts
while the browser is running (so we get a flurry of notifications that
trigger repeated, overlapping updates to our font list). This is
probably not a common situation -- most users aren't installing and
removing fonts frequently in the midst of a browser session -- but
still, I'd be reluctant to ship something that is known to be crashy in
such a scenario.

So I'd definitely prefer to have bug 1667977 fixed before it rides to
Release. I've been attempting to debug but it's proving difficult to
track down the root cause at the moment. (Not having a tool equivalent
to rr or pernosco on Windows hurts...) I'll try to spend some more time
digging into it this week.

Reply at:

On 2021-03-10T18:28:55+00:00 Cpeterson-3 wrote:

(In reply to Jonathan Kew (:jfkthame) from comment #3)
> So I'd definitely prefer to have bug 1667977 fixed before it rides to Release. I've been attempting to debug but it's proving difficult to track down the root cause at the moment. (Not having a tool equivalent to rr or pernosco on Windows hurts...) I'll try to spend some more time digging into it this week.

A fix for SearchAllFontsForChar crash bug 1667977 probably won't be
ready for 88 Beta, so I will move this bug from Fission milestone M7 to

btw, the reporter of bug 1667977 says the crash is also reproducible on
Linux, so you may be able to catch the crash in rr on Linux.

Reply at:

On 2021-04-10T11:18:58+00:00 Jfkthame wrote:

This has been enabled on Nightly since 82, and also early Beta since 83.
Now that a fix for bug 1667977 has landed, I think we should remove the
early-beta condition and let this go all the way to release.

Reply at:

On 2021-04-10T11:20:16+00:00 Jfkthame wrote:

Created attachment 9214874
Bug 1694174 - Pref-on the shared font-list by default for all channels. r=#layout-reviewers

Reply at:

On 2021-04-10T22:06:18+00:00 Pulsebot wrote:

Pushed by jkew at mozilla.com:
Pref-on the shared font-list by default for all channels. r=emilio

Reply at:

On 2021-04-11T09:36:06+00:00 Cbrindusan wrote:


Reply at:

On 2021-06-07T09:39:49+00:00 Pascalc wrote:

Jonathan, we have already 4 regressions reported in 4 days since we
shipped this feature in 89, among them 2 marked as S2 + a medium
crasher. Should we consider deactivate this feature in a 89 dot release?

Reply at:

On 2021-06-07T10:26:14+00:00 Jfkthame wrote:

If we're going to do a dot release, we might want to consider
deactivating on Linux due to bug 1714282, which I think is actually the
most serious issue we've seen. A patch has landed there (which I hope to
uplift to 90), but for 89, I'd consider disabling it.

The crash on Windows (bug 1689379) is probably not too big of a concern;
it's specifically at shutdown, and it's not really a "bug" that's
crashing us, it's a timeout because directwrite is being slow, which we
then detect as a hang and deliberately crash. Again, a patch has just
landed, which I hope to uplift to 90. I suppose for 89, though,
deactivating via the pref would be a better user experience.

I think the other issues were categorized as S2 simply due to being
"regressions", but may not be so serious - there are several examples
where users have odd font configurations, and have experienced a change
because our behavior arguably became *more* correct; I don't think these
type of edge cases would justify reverting the feature.

So - yes, I think deactivating in an 89.x dot-release, while we wait for
bug 1689379 and bug 1714282 to be fixed in 90, may be a good option

Reply at:

On 2021-06-10T21:47:47+00:00 Jfkthame wrote:

Created attachment 9226420
[patch for 89.x dot-release only] Disable on Linux/Windows

I'm not sure how to manage a patch intended for dot-release-only in
phabricator, so simply attaching it here.

Approval Request Comment
[Feature/Bug causing the regression]: 1694174
[User impact if declined]: see regressions: bitmap font issues on linux; crashes for linux users with huge font directories; possible windows shutdown hang
[Is this code covered by automated tests?]: no
[Has the fix been verified in Nightly?]: simply reverts to earlier behavior
[Needs manual test from QE? If yes, steps to reproduce]: -
[List of other uplifts needed for the feature/fix]: -
[Is the change risky?]: no
[Why is the change risky/not risky?]: revert to previous code via pref flip
[String changes made/needed]: -

Reply at:

On 2021-06-11T10:06:40+00:00 Pascalc wrote:

Disabled on 89

Reply at:

** Changed in: firefox
       Status: Unknown => Fix Released

You received this bug notification because you are a member of Mozilla
Bugs, which is subscribed to firefox in Ubuntu.

  Firefox 89 won't load pages due to many fonts

To manage notifications about this bug go to:

More information about the Ubuntu-mozillateam-bugs mailing list