We are aware of the issue and tracking it in a thread in bug-reports.

Thanks.