Thanks for the reports! We’ve managed to track down the cause here, and have a fix on the way:
This will also be backported to the recently-released stable version.