Not that it’s necessarily a solution to your problem, but have you checked to see if the same issue arises in the v4 beta?