The team now acknowledged the problems on Twitter and is said to be working on fixes: https://twitter.com/sourcetree/status/699624992003244033
("Funny" that this is the first public mention of @sourctree of any update - nothing on the blog, Twitter feed...)