Fixed by rev#81296
This correction will be available in next 6.5 release.