This issue should be fixed in the version 5.3.
Meanwhile, you can test the correction with the version 5.3 beta 7 available here.