It's a known Chrome + Windows issue at the moment - still trying to figure out how to best resolve it without failing back to just web safe fonts.