Ah, I did see this once. I thought I fixed it, but apparently I just did not find the conditions under which it occurs.

I have encountered things like this, and I know it's got to be a pointer I forgot to reset. I will look for it and hopefully fix in the next update. Thanks!