That might be from a similar coding error- see if it's fixed now!
It appears to be fixed! Will report otherwise if it happens again, but good work with the hotfixes so far. ^_^
