All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=593645

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_5KaogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_4G4rwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_4aYtAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_9TRvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_9nouAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_5KMvQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_6vrrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_77EsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_42GtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDAv_f0oAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA__OPuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_63BuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_9TopAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_6TqqQoM


Bot(s) for this bug's original alert(s):

chromium-rel-win10
chromium-rel-win8-dual
win-zenbook

This looks to have recovered. Looking at the graph it seems pretty clear this regression was caused by "Initialize the font fallback when the direct write font
manager is created." https://codereview.chromium.org/1740533003 - the regression happened when this CL landed and recovered when it was reverted. 

+kulshin@ and bungerman@ as FYI, but closing as fixed now that it has recovered.