This is a known issue that is being investigated. It was already reported here:
Hopefully a fix will be available soon.