Haha. I encountered that bug as well, but could never pinpoint where it was coming from! I thought I had patched it because it didn't come up during my last few tests. Thanks for bringing that to my attention, and just commenting in genral!
