Guys: this is a really weird issue, and not one I've been able to recreate. That said: I just talked with the entire support crew about this, and all of us have seen some variation on it reported since the release of 2.0.11.
I've got the devs looking into this now - it seems we may have introduced some problematic code in 2.0.11, which explains why it wasn't occurring for some of you in 2.0.10. It might make sense to downgrade in the interim, which I apologize for, but know that we're working to patch it so this shouldn't be an issue for long. Once I hear back regardless, I will pass an update your way.
Thanks for your patience and support so far. If you need anything in the interim, don't hesitate to contact me (pro a/ tri.be) and we'll do our best to assist.