This bug is fixed in revision#68809.

Thanks for your report.