This bug is fixed in revision#69312.

Thanks for your report.