Thank you for your report/contribution.
This issue is now fixed by revision rev#75838