"push changes immediately to origin/master" flickering and unusable

My repos connected to bitbucket.org in sourcetree frequently get into a state where "push changes immediately to origin/master" starts flickering and becomes unusable without closing sourcetree and opening it again.   

It kind of feels like the software has been designed to do a denial of service after against bitbucket.org or gets in a infinite loop of some sort in recent versions.   With the bitbucket.org service being unavailable occasionally sometimes, It makes me wonder if the sourcetree client is the cause of this, since it seems to do tons of actions against bitbucket, which maybe should be reduced to a slower/controlled polling period and only for the currently active repo.  I'm just guessing on that, but it's definitely broken at least at the UI level.

Other bugs frequently observed:

The interface is often reporting wrong information for push/pull number. 

Often have to hit F5 to refresh views since the default refreshing is not good enough.

On another computer here, it is impossible to override the user you commit as on the global level, every repo has to be overridden.  Even after wiping out hidden files in appdata, it comes back somehow as the previous user.   I've reinstalled from scratch twice and can't figure it out.

The sourcetree program is able to crash instantly if you delete the .git folder for a repo that is already open.  Sometimes I clone and move them and this is annoying.  It should just close and mark it inaccessible instead of dying.

I've really tried to be patient for a release that fixes these issues, but it doesn't seem like it is coming so I'm reporting them myself.  I've seen at least 5 or 6 version upgrades yet the same problems persist.   We've been struggling with sourcetree bugs for at least 6 months.   I'm used to the new 2.0 layout now, but the bugs with common operations are very frustrating.  Sourcetree will be a good program whenever it gets stable again.