This bug is fixed in revision#71176.

Thanks for your report.