I am not saying the bugs are easily encountered, however when they are the severity is too high.
I was running fine for a week on 1747, then this issue occured.
I was able to reproduce the problem, ONCE I got TS in that state.
After re-installing, I have not had the problem. Clearly it is a difficult bug to track down, but they have enough pointers to find it now IMO.
But it goes to show how difficult it is for them to make releases. They probably lack a fully staffed Test Team. 1:1 Ratio Test-Dev is what MSFT uses, industry average is .15:1.
If one wanted to test something like this, a simple preliminary regression suite would be to get every workspace sent to Support. Then create a macro that opens it, saves it, closes it, then reopens it. Run this on a debug version with "asserts".
Understanding the SaveAs code paths would help to refine the test suite. Since this is such an obvious test to run, it is clear they are not up to snuff yet.
Solution: Don't expect much and back up all data on a weekly basis. Also I would suggest clean installs and not upgrades.
-Cheers
PS: also remember that rolling releases like this are frought with regression bugs. Assume for every 3 bugs they fix, 1-2 will be introduced. They should be lesser in severity tho...