Hey everybody.
I’ve merged all these threads into one – I hope you don’t mind (I really don’t want to be posting the same answer on 5 topics).
Thank you for the reports. The right team has been notiffied. Kudos to @sylvainhalle for an excellent summary of the issue (and finding what is most likely the root cause).
The workaround he mentions should indeed address the issue temporarily.
When there is a further update on this, we will come back on this thread.