This bug is fixed in revision#69432.

Thanks for your report.