I have exactly the same issue on production chrome. Started happening a week ago. Were you able to find a workaround?