Thanks for the reporting this. We are working on it. It seems that this issue exist for a particular chrome version. We'll fix it soon.