I have updated the attached test case to current version (4.3.5-Final).
It seems that the bug still exists there.