Hi, folks - I wanted to check in on this one. There are a number of situations that cause this same error that have been addressed since this bug was first reported.
We are continuing to work on dealing with them all -- It's highly obvious that the original problem was never fully contained, and equally obvious that there are now more severe cases as well.
This is an issue that's very important to us to catch.
- Scott
LINK