Perhaps it was related to this known issue. So, hopefully it’s resolved now. And, if not, file a bug report.
