This bug is fixed in revision#69176.

Thanks for your report.