Hi IEQI,
This is still under assessment by development staff. Unfortunately I do not have a timeframe of when a fix will be implemented as our resources are currently dedicated elsewhere. I have updated bug report to reflect that additional developers are experiencing this error.