#2 - June 29, 2016, 5:58 p.m.
Good news, everyone! We have narrowed down this issue and have a working fix that we are currently testing.
Unfortunately, due to the complexity of the fix, it will not make it into the beta build until next week. Apologies for the frustrations in the meantime.