We no longer maintain 4.x. If the same issue happens in 5.0 We can address it there. Please try against 5.0 and see if the same problem occurs and attach a test as necessary. Issues that do not effect 5.0 (or are not verified to affect 5.0) will be rejected.