Source-Tree 2.0.20.1 keep crashing right after start

[Frank Fock]

After installation of Source-Tree it runs once. Then after exit and a fresh start it appears but at the same time immediately crashes with:

Problemsignatur:

Problemereignisname: APPCRASH

Anwendungsname: SourceTree.exe

Anwendungsversion: 2.0.20.1

Anwendungszeitstempel: 5910598c

Fehlermodulname: git2-785d8c4.DLL

Fehlermodulversion: 0.24.0.0

Fehlermodulzeitstempel: 56d9a1cc

Ausnahmecode: c0000005

Ausnahmeoffset: 0000000000021103

Betriebsystemversion: 6.1.7601.2.1.0.256.4

Gebietsschema-ID: 1031

Zusatzinformation 1: 3e17

Zusatzinformation 2: 3e1714e5fcbcaa4a78fade95c83df052

Zusatzinformation 3: 0d05

Zusatzinformation 4: 0d05273131234648987bb72a10835966

Other tools and git command line are working on the same system. An old version (before 1.9) worked too. I cannot use SourceTree anymore and had to switch to some other Git-UI.

　

[s@110]

move or remove .git directory from your home directory, if you haven't tried yet.

[Frank Fock]

The crash still happens with version 2.1.2.5 after the Application has been exited for the first time. Then right after starting it, it keeps crashing at a 100% rate:

Problemsignatur:

Problemereignisname: APPCRASH

Anwendungsname: SourceTree.exe

Anwendungsversion: 2.1.2.5

Anwendungszeitstempel: 59354ffa

Fehlermodulname: git2-785d8c4.DLL

Fehlermodulversion: 0.24.0.0

Fehlermodulzeitstempel: 56d9a1cc

Ausnahmecode: c0000005

Ausnahmeoffset: 0000000000021103

Betriebsystemversion: 6.1.7601.2.1.0.256.4

Gebietsschema-ID: 1031

Zusatzinformation 1: 3e17

Zusatzinformation 2: 3e1714e5fcbcaa4a78fade95c83df052

Zusatzinformation 3: 0d05

Zusatzinformation 4: 0d05273131234648987bb72a10835966

[Den Thorn]

I had similar issue - ST run only once ok (right after install), then every single nexyt startup it gave me up to 4 messages "git status fail 128 must be run on the working tree (c:\Users\MYUSERNAME) "  and crashed after that.

I created an empty .git folder inside c:\Users\MYUSERNAME and it fixed crashes, now it works ok

Cheers!

[James Wilkinson]

I've experienced the same issue after updating to v2.0.20.1 yesterday.

I tried uninstalling and reinstalling SourceTree, but the error persisted. After several attempts, I managed to capture the error popup:

---------------------------
Error encountered
---------------------------
'git status' failed with code 128: fatal: unable to access 'H:\/.config/git/config': Invalid argument
 (C:\GitHub\<reponame>)
---------------------------
OK   
---------------------------

H: is a network share at my office, but I am working remotely today and don't have access to the office network. Previously I was using SourceTree v1.9.10.0 and this issue was not present.

Why does SourceTree save a config file to a network share instead of locally and where can I change this? 

[minnsey]

That is actually a git config file not aactually a SourceTree one.

Git does save configuration files to user's home directories.

You mention v1.9 worked in this environment, in which case it may be a difference between git.exe used in <=1.10 and libgit2 used in >=2.

[Ana Retamal]

Hi Frank, our first guess is that this could be caused by a corrupt user.config in %localappdata%\Atlassian\SourceTree.exe_url_\hash\2.0.20.1\user.config. Can you try removing/backing up that file, restarting and see if it works?

If it still doesn't, it would be helpful to have a look at the sourcetree.log files. You can find them as explained at SourceTree logfile location. Please submit your logs via a Support ticket and let us know here you did that, so we can proceed accordingly. Remember to include your Windows version.

Best regards,

Ana

[Frank Fock]

I have removed the whole %localappdata%\Atlassian\* stuff several times. That does not change anything. Even *not* configuring any Git repositories at the first successful start after fresh installation will *not* prevent Sourcetree from crashing after second (and more) start. Windows version is 7 Enterprise (see crash report above).  

The sourcetree.log file is completely empty - so no need to upload it ;-)

[Richard Taylor]

I have the same problem, though only in some of my repos.

Note that git2-785d8c4.dll appears to be LibGit2 v0.24.0 from May 2016.  This is more than 1 year old, and LibGit2 is now on v0.24.6 with several security related releases including fixes for at least 2 CVEs.

To be honest it's a bit concerning to be forced to upgrade for security reasons and find that the new version (a) crashes, and (b) has out of date libraries with known security issues.

[minnsey]

We are currently testing a SourceTree update with updated dependencies

[Richard Taylor]

Excellent, can I test it when it is available, or is it already available through the beta track?

[minnsey]

Hi Richard,

A release should be available in the beta group next week.