Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

git.exe fsmonitor process did not exit after close sourcetree


On windows, Sourcetree.exe will start "git.exe fsmonitor--daemon run" process for every local repository(even not opened in tab), I didn't found how to disable this feature, and what's worse, those process will keep running/existing after I close/shutdown the SourceTree.exe, and it'll prevent any action on my local repository folder, I have to kill them all one by one in task manager. It's strange, and kind of bug.

Additional info:

  • SourceTree version: 3.4.7
  • git version:
  • OS: Window 10 Professional 1803 (17134.1304)

1 answer

I have the same issue.

wmic process where "commandline like 'git fsmon%'" get processid, commandline

returns 65 processes. To kill them after sourcetree closed I use

wmic process where "commandline like 'git fsmon%'" call terminate

Playing around with the settings it seems that if I disable the "General" option "Refresh automatically when files change" sourcetree will no longer start all these processes.

I tried doing this for individual repositories thinking that changing the option to automatically refresh (Miscellaneous section) might have an impact but I could not be sure. After disabling the above global property, re-enabling it did not seem to start the processes anymore...

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events