This bug is fixed in revision#69171.

Thanks for your report.