This bug is fixed in revision#69362.

Thanks for your report.