Seems like this issue is not reported anymore in artifacts from builds #359, #365 and #368 ; while it was on build #351....

I'm not sure what fixed it. Waiting a couple weeks more to make sure it's not a flicker.