The 4.2 branch is no longer being actively maintained and therefore it'd be helpful if you could see if the problem continues to persist on 5.x.