Fixed by revision rev#72871, the correction will be included in next release.
Thank you for your report