Crash on commit

[Dave Grandon]

Hi, it seems that every time I commit atm SourceTree crashes, I did a search here and the only solution I could find was to delete a draft commit message but I don't have one ( see attached  )

It appears that my commits are working as can see my changes in Bitbucket but very annoying that it crashes

Cheers 

sourcetreeconfig

[Jörg Rösner]

Basically, I had the same issue. The error occours because no .gitconfig will create during the setup of 3.2.4. or you have missed to check the checkbox to create user information during setup wizard.

Open Sourcetree and check "File status" - you will see that there no user is available:

Fix the Issue

Close Sourcetree

To fix the issue open the explorer and navigate to: C:\Users\

Open the folder with your username

In this folder you should have a file with name ".gitconfig". If the file not exist, create it (It is no typo, the name will written with the dot at the beginning of the filename: .gitconfig

Open the existing / new file with an editor and add the following lines to the end of the file

[user]
name = User
email = Email

For "User" use a standard name (It is not the Windows Username meant)

For "Email" use a standard email Address

Save the file and start Source Tree again. You will see now, that a user is available in the "Status History".

BTW.: You can find your old user data in your last commits:

Go to "History" and select a commit. Here you can see in the commit information for the "Autor": Your old data. You should use the the same data as before to keep the structure:

Greets CR

[DjdjHacks]

It works.

[carlcortez]

Thanks :D

[Patrick Klein]

Thank you so much!!!

[Bart Van Hoecke]

thx!

[Hrp]

3 years, no solution. you know, there are other free solutions out there

[Gudakesh]

it was crashing for me upon using Sourcetree v3.2.6 moments ago, so i rolled back to Sourcetree v3.1.2 and now everything is working just fine. Hope that helps!!

[Maciej Kolosko]

v3.2.6 crashed on commit. Reverted to v3.1.3 on windows, and it works. Thanks for the suggestion.

[Gudakesh]

i am glad it helped :)

[Gabe Chavez]

I'm giving GitKraken a try.  I love SourceTree, but downgrading to get it to work is just sad.

[Gudakesh]

i agree, let's just hope it get's fixed in upcoming release

[Allan Li]

You can revert back to previous versions here -> https://www.sourcetreeapp.com/download-archives

No need to uninstall your current version, just download 3.1.3 and run the install (at least on Windows), and it will overwrite the new version.

[hawkenking]

same on 3.2.6

ridiculous as usual

[khangb]

Thanks guys. Reverted to v3.1.3 and it did the trick.

[Aggressor]

Crashing for me as well will revert

[dabeschte]

Having the same problem and downgrade also did the trick for me, The problem is probably related with the pop-up that sourcetree shows if you did not configure git (name and email), because this was the first thing that I saw when I hit the commit button in the downgraded version.

edit: just noticed that Aggressor came to the same conclusion.

[koendebrabanter]

Same problem, and reverting to v3.1.3 did the trick. But as already mentioned, it is sad that this is necessary.

[James Lenon]

I was able to keep using v3.2.6 by setting my Git name and email address in the global .gitconfig.  This stopped the popup which was crashing Sourcetree.

[user]
name = Some Username
email = someuser@gmail.com

[Deleted user]

Fix my issue. Thanks a lot!

[Christine Spencer]

James Lenon, that did the trick. Thanks!

[Alin Baesu]

I also had this issue with 3.2.6, and it seems it has to do with credentials.

You should have the Full Name and Email address fields filled in Options, under Default User Information.

However, in case these fields are already populated and it still crashes on commit, you should leave them blank, make a commit (it will crash), then restart Sourcetree and fill the name and email address again, and that might solve it (it worked for me).

[Peyton Davari]

This works, I didn't have to revert the sourcetree version or anything. 
As Alin suggested, 

Just go to tools -> options and then edit the name and email address fields to leave them blank. Restart. Return to tools -> options and fill the name and email address. Restart again. Then everything worked for me :)

[Ewald Ramp]

No need to downgrade!

1. Go to `C:\Users\{your user}`
2. Find `.config`. If it does not exists, create it
3. Add the following into it and save it

   [user]
       name = Your Name
       email = your@email.com

4. (Re)start Sourcetree 3.2.6

[Aggressor]

I think the crash is related to not having credentials set. The latest version worked on other pcs I had but it crashed on a new one I was setting up. When I switched back to 3.1.3 it asked me for my credentials before committing, whereas the most recent version just crashed. 

[Johannes Gerk]

Had the same issue, reverted to 3.1.3, which worked, went back to new 3.2 and now that doesn't crash anymore either... might be an account/authentication issue as suggested by others.

[Maciej Kolosko]

I can confirm same thing happened for me. I upgraded back to 3.2.6 after initial downgrade to 3.1.3 and things are working fine since.

[miguel_brito_globaltronic]

Confirm same result. 

[Aaron-IPV]

I have been noticing massive CPU spikes/ cores pegged at 100% when committing in the 3.2.6 version, and occassionally 'Git for Windows' going past 100% cpu as well even after closing source tree. Downgrading to 3.1.3 (and also going back to 3.2.6 after) hasn't appeared to solve the issue for me, and I have global gitconfig user settings already in there. 

[Aaron-IPV]

Just updated Git to version 2.23.0 and it hasn't helped either.

[sbreukink]

For me this issue started occuring right after I installed MS visual C++ Build tools (it was working fine before), but downgrading to 3.1.3 solved it.

[Jared Steffen]

Still not fixed

[Allan Li]

Sep 2019 - I rolled back from 3.2 to 3.1.3 over here https://www.sourcetreeapp.com/download-archives and it worked

[Jonathan Osborne]

This is not fixed in 1.9.10.0.  Sourcetree just crashed on consecutive commits.

[ribbetbit]

If you have multiple repositories opened, moving all to the "File Status" view prior to committing seems to prevent the crash.

[Thomas Geijtenbeek]

There seems to be a bug report for this issue, please upvote so it will be fixed sooner!

[Liza Tymchenko]

Same here! Plus mine crashes even when I commit from the "File Status" view. No actual fix yet?

[Luuk van Aggelen]

Same here. Workaround as mentioned by Vincent Barral works perfectly, but it's quite annoying. 

[Thomas Geijtenbeek]

Me too! I'm using Alt + Shift + C to commit.

[Jon Champlin]

Same problem here

[Till Riemer]

same thing here, but it indeed works fine if commiting from the "File Status" view!

[ribbetbit]

We have the same issue. I do a commit/push, it crashes, I restart SourceTree and can then complete the push without crashing. Started happening about 2 months or so ago.

[Jon Marks]

Same here. Happened since the last Sourcetree update. All my fellow developers using different source control clients are laughing at me.

[Vincent Barral]

I found a "workaround":
crash does not happen If I do the commit from the "File Status" view.


 

[Scott]

Ditto.  This just started happening in the last couple of weeks.  It seems to commit, but crashes every single time, and it's really getting annoying.  Please fix this!

[Stephan Flick]

Same here. Please fix the bug!

[Remi Vangreveninge]

Same here crashes after commiting, commit is done but i need to restart source tree to push

[Vincent Barral]

Same here.

[Lishan Luo]

Same here. Is there a fix yet?