A similar issue started happening at some of the implementations after chrome got auto upgraded to version 65 recently. I think its specific to chrome on Windows. I came across the following threads
https://productforums.google.com/forum/#!topic/chrome/UmU9hX84KV0
Based on suggestions in the thread, going to Canary release fixed the problem for now. so guessing that next chrome upgrade will have the fix.
FYI, in case other implementations face this.