SourceTree repeatedly losing track of index.lock

Every time I try to make a change in my branch, SourceTree creates an index.lock file in the .git directory, then refuses to make the change because an index.lock file exists. Deleting the lock file doesn't help, as SourceTree will just create it again. Any suggestions?

11 answers

This widget could not be displayed.

i see the same thing after i tookthe sourcetree update.

This widget could not be displayed.

Ditto.  Let me know if anyone finds a solution.

 

This widget could not be displayed.

Ditto - same exact issue.

This widget could not be displayed.

Still a problem in v1.9.6.2, especially interactive rebase. Please vote on this issue to get someone working on it: https://jira.atlassian.com/browse/SRCTREEWIN-5639

This widget could not be displayed.

I just did an update to 2.6.3 and the index.lock issue is back again! It seems that Sourcetree creates the index.lock, then does the commit or whatever task you trigger, and at the end does not delete index.lock anymore. I manually have to delete index.lock every time I trigger an action. When will this be fixed?

This widget could not be displayed.

I have the same issue with 2.6.3. 

It is annoying to delete index.lock by hand after every activity.

This widget could not be displayed.

Same here with 2.7. That really sucks! Atlassian please fix it. That would save my x-mas days.

This widget could not be displayed.

Getting this in v2.4.7.0 on Win10. 

Edit: It started working again right after I posted this so I think it's an intermittent issue.

This widget could not be displayed.

Getting this in v2.4.7.0 on Win10 time to time.
SourceTree creates and removes git.lock file repeatedly. 

This widget could not be displayed.

I still see this on 2.7.1 on macOS very regularly. I think it's a race condition somewhere in source tree as sometimes it causes it and sometimes it can sort itself out.

I have had success with closing sourctree and deleting .git/index.lock from the command line

This widget could not be displayed.

I'm also seeing this VERY frequently in 2.7.6 (macOS 10.12.6). Has being occurring intermittently for quite a few versions now. Seems to be most common for me when the system is under high CPU load from other processes.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Published May 30, 2018 in Sourcetree

Tip from the team: configuring Git or Mercurial in Sourcetree

Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...

727 views 1 3
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you