Uploaded image for project: 'Sourcetree for Windows'
  1. Sourcetree for Windows
  2. SRCTREEWIN-6049

Lock file gets stuck, restarting source tree fixes it.



    • Bug
    • Status: Closed (View Workflow)
    • Low
    • Resolution: Duplicate
    • None
    • Git
    • source tree, linkage to stash, java 8.91, windows 7 x64.

    • Severity 3 - Minor


      It seems to be random, but on occasion a repo I am working in will have an error where it states the lock file could not be created due to it already existing, and prevent git actions to that specific repo. Restarting source tree seems to fix the error (at least source tree works again and no longer shows the error). No other clients are running, and while I do have git integration on visual studio this has happened to repos that do not have content involved in visual studio solutions/projects.
      I am unable to replicate the issue reliably, it seems to happen at random.
      The message appears similar to the error referenced in SRCTREEWIN-5010, however I do not rebase these repos.
      If the error occurs appears again I will append a copy of the error and state if the lock file does actually exist, for now it is a waiting game until it happens again. Normally this issue arises about twice a day, so it should not be too long.

      git -c diff.mnemonicprefix=false -c core.quotepath=false checkout ~~~~~~~~
      fatal: Unable to create '~~~~~~~~~/.git/index.lock': File exists.
      If no other git process is currently running, this probably means a
      git process crashed in this repository earlier. Make sure no other git
      process is running and remove the file manually to continue.

      The lock file does not actually exist.

      I can not find a reliable way to recreate the failure, I found a repo that seems to fail somewhat frequently, however it is still intermittent.


        Issue Links



              Unassigned Unassigned
              2a28b948be03 Daniel Miller
              0 Vote for this issue
              2 Start watching this issue