You are right I was able to setup a testcase. Unfortunately the error does not occur with 5.2.2, whereas the testcase can successfully reproduce the error with 4.2.21