I'll check it for the next update, but I can't find a way to reproduce this error, nor anyone else has reported it.
