This bug is fixed in revision#69173.

Thanks for your report.