Thanks for your report.
This has been fixed at rev#69313.