This is a duplicate of #1231, which was erroneously closed by @carsonRadtke who said that the fix was included in 4.2.1.

The following comments make it very clear that the fix was not included in 4.2.1.

The issue still reproduces in 4.2.1.