I have yet to reproduce it again since doing updates soon after the report, so I assume this has been fixed.
I have yet to reproduce it again since doing updates soon after the report, so I assume this has been fixed.