This bug is fixed in revision#69102. Thanks for your report.