This bug is fixed in revision#69519.

Thanks for the report.