Occasionally, when switching to the Log view, I will find that a commit somewhere far down the list (my repo presently has 560 commits) has been multiselected in addition to the latest commit. This causes SourceTree to show a diff view between that commit and my working copy. For some reason, this multiselect cannot be cleared by just clicking on another commit with no modifier keys; I have to scroll down to the commit that was inappropriately selected, and only then can I clear the selection.

I've been able to reproduce consistently with these steps:

1. Make changes to two files.
2. Switch to File Status view.
3. Separately stage and commit each file's change.
4. Switch back to Log view by clicking master branch on left.
5. Mixed reset to first commit.
6. Stash.
7. Mixed reset to first commit's parent.
8. Select Working Copy on left.
9. Stage and commit file.
10. Apply the stash from the left pane.
11. Switch to log view by clicking master on the left.

Another entry will be inappropriately selected at this point. It seems to always be about halfway down the list, which I suspect is an artifact of the number of commits I have; SourceTree will sometimes say it's loading 300 commits, which would put it at about the halfway mark. When the repo was smaller, I remember seeing this issue, but then the inappropriately selected commit was near the end.