Thanks for the reports. I now have this bug listed on our release notes page along with a test case which regularly triggers it for me, and am working on fixing it. Ken