Fixed by revision rev#77451

This issue is now fixed for future 6.4 release.