This is a known issue that was caused by changes in the Chromium code:
We should have a fix for this soon. See this comment for the current workaround.