This page loads without a problem on Safari (see screenshot).

This pages loads on Chrome Windows - the characters are still the Unicode boxes, but it loads quickly. On the Mac it takes a long time to load, and scrolling down takes a long time.

Taking a stab at the appropriate components.

Deleted: Screen Shot 2016-07-12 at 12.04.25 PM.png 159 KB

	Screen Shot 2016-07-12 at 12.04.25 PM.png 159 KB View Download

An unfortunate case of a large font stack, consisting of 5 fonts: 
Consolas, "Liberation Mono", Menlo, Courier, monospace; 
plus OS X' fallback API not returning a font other than "Last Resort" for runic characters. There are also no spaces between the runic words. All combined, this makes shaping very slow.
This could be improved:
* by introducing a level of manual fallback tweaking on Mac, similar to what we have on Windows? 
* if not finding a font at all, by having a cache for characters for which no fallback font was found in order to avoid the expensive system call.

I've also tried adding fallback code similar to FF' using CTFontCreateForString instead of our NSFont findFontLike approach, but we also only get "LastResort" from that call.

I'm seeing similar behavior on the following page, but with emojis: http://apps.timwhitlock.info/emoji/tables/unicode

Could it be the same issue? I don't see either of these issues on another machine, though, so it might be hardware/driver specific.

I'm on Windows 10, btw, and see the issue.

Dropping Blink>TextEncoding label since this is just font-related (unless I'm misunderstanding)

I can no longer reproduce the "unresponsive" error in Canary 55.0.2868.0 on either
https://gist.github.com/huw/8a564d1e8027294df15d
http://apps.timwhitlock.info/emoji/tables/unicode
though first paint isn't very fast and scroll a bit sluggish.

Stable 53.0.2785.116 is much slower than Canary but not as slow as "unresponsive" error.

Can anyone still see the slowness in Canary?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This is now quite a bit faster but still rather slow.

LayoutNG will make it significantly faster still, on par with other complex script.

No other improvements are planned until then.