Gave it a look and while I'm having trouble replicating the bug, I can tell what line of code is responsible for that thanks to the error message. Also noticed another minor issue that I'll solve at the same time; I'll have a patch out as soon as possible.