1659635 - Significant delay on page loading (with "no response" on window title)

Status: RESOLVED DUPLICATE of bug 1669855

(Core :: Layout: Text and Fonts, defect)

Description

[blinky]

+++ This bug was initially created as a clone of Bug #1648355 +++

This was reported in bug 1648355 comment 15 and comment 0.

Steps to reproduce:

1. Download and install all Google Noto Fonts.
2. Download Font Loader.
3. Download Franklin Gothic Book Regular.ttf.
4. Open the Font Loader, Click on the Add Fonts button, Select the font file Franklin Gothic Book Regular.ttf then click Open.
5. Click on the Load button.
6. Open attachment 9100780 [details].

Profiler data https://share.firefox.dev/3kVR51m

Comment 1

[blinky]

This also happens on startup.

Steps to reproduce 2:

1. Download and install all Google Noto Fonts.
2. Open Firefox.
3. Open attachment 9100780 [details].

Profiler data https://share.firefox.dev/2CAIzn0

Comment 2

[blinky]

Regression range:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=47d7c18620c845c3a42610fea5468ccc50889bae&tochange=82274c20257455ffb7ea74404ee9d27bc4246819

Regressed by: bug 1588407

Comment 3

[blinky]

This was reported in bug 1648355 comment 15 and comment 0.

Comment 4

[Ting-Yu Lin [:TYLin] (PDT, UTC-7)]

I suppose this is still an issue even with the fix in bug 1648355.

Comment 5

[Jonathan Kew [:jfkthame]]

Yes, this is triggered by the search for "legacy" styled family names (Arial Black, in this case) rather than by character fallback.

Comment 6

[blinky]

I can also reproduce in the test cases below with the steps in comment 0 and comment 1.

data:text/html;charset=utf8,<div style="font-family: arial a">test
Profiler data https://share.firefox.dev/32kTUjO

data:text/html;charset=utf8,<div style="font-family: Noto Sans Extlt">test
Profiler data https://share.firefox.dev/2Qs68BS

Comment 7

[Jonathan Kew [:jfkthame]]

After the patches in bug 1669855 landed, I believe this should no longer be an issue with current Nightly. The content in these examples may render with a fallback font for a brief period (a second or so, on my machine, but could be longer on a slower system or with a huge number of installed fonts), but should not block the browser with "no response" any more.

Blinky, can you confirm the behavior is now as described above? If so, I think we can close this. Thanks!

Comment 8

[blinky]

I confirm this bug has been fixed in bug 1669855. Thanks.

Comment 9

[Jonathan Kew [:jfkthame]]

Great, thanks! Sorry it took a while to get a solution in place for this one. Dup'ing forward to the bug where the issue was eventually addressed.