This bug is fixed in revision#71436.

Thanks for your report.