Same problem here. It showed up again after Command + Tabbing out of Chrome and switching back in. It's humorous that the custom cursor fails in the one case where it's identical to my default cursor.