Thanks for sending us the info.
Just wanted to provide you with an update of this issue. We have an existing support case (#881991-1) open for this. The defect has been confirmed, and we have someone in the dev team currently working on a fix for this issue. Any further communication will be going through our support team.