I may have figured out a workaround for this issue. I poked around the checkin history...
No change in current version (5.2.1 (build 4428))
I have also been getting the same error since 5.x beta (including the current release...