Fixed by revision rev#66512.
The correction will be available in next release.