I'm seeing this in SourceTree for Mac 4.2.8 , Sonoma 14.6.1. I may have had SourceTree open for a week. In that time I have probably opened 20 repos, and kept 2 open for a long time. These 2 are pretty large, with >10,000 files and >10,000 commits.

7612c40a640a ,

Thanks for your comments. We will try to analyse provided info and check what might be wrong.

Hi Raman,

Thanks for the detailed response. To answer your questions:

1. How many repositories you have added in Sourcetree?
   • 3 repos, though I only use one most of the time.
2. Are you using repositories with submodules?
   • No
3. How long it takes for this issue to occur on your machine? (time from starting Sourcetree, till issue occurs, some estimated time, like 1hour or 1 day)
   • I don't know for sure, but it's definitely in the days to weeks range
4. Maybe you could notice, which operations in Sourcetree you are performing most frequently? Or this issue occurs even Sourctree is idle?
   • I tend to see this error when Sourcetree is refreshing the Git repo history (so I assume fetch) or when trying to pull/push.
5. Which macOS version is installed on your machine?
   • Sonoma 14.0
6. Which platform you are using (intel, arm)?
   • ARM (2021 16" MacBook Pro M1 Max)
7. Which git version is configured in Sourcetree settings: system or embedded?
   • Embedded Git 2.41.0
8. Maybe you have some observations, which you think could help to understand some sequence of appearing this issue?

• • I'm guessing that I'm encountering this issue because I leave Sourcetree open on my macbook whilst I work. I guess I should get in the habit of restarting Sourcetree regularly.

Hi, 7612c40a640a 

Yes, just checked, we've provided the fix for this in 4.2.3.

The thing you are still experiencing this issue are resulting into two assumptions:

1. A regression from our side, which lead to situation when fix is broken and this issue happens again.
2. Initially we identified not all cases when this issue could occur and fix was partial.

In both cases I will require your help to get additional information about this, because I haven't seen this issue on my machine for a long time, which means some troubles with reproducing it. Could you please answer these questions:

1. How many repositories you have added in Sourcetree?
2. Are you using repositories with submodules?
3. How long it takes for this issue to occur on your machine? (time from starting Sourcetree, till issue occurs, some estimated time, like 1hour or 1 day)
4. Maybe you could notice, which operations in Sourcetree you are performing most frequently? Or this issue occurs even Sourctree is idle?
5. Which macOS version is installed on your machine? 
6. Which platform you are using (intel, arm)?
7. Which git version is configured in Sourcetree settings: system or embedded?
8. Maybe you have some observations, which you think could help to understand some sequence of appearing this issue?

Possible workaround
There is also small chance that it may occur because browser.plist configuration file, which exists for a long time and got bugged after multiple updates. What you could do is try to cleanup it to check if it will help.

Warning: it will lead to cleaning up list of repositories added into Sourcetree.

To do this, perform these steps:

1. Quit Sourcetree
2. Go to ~/Library/Application Support/SourceTree/ directory
3. Find browser.plist
4. Rename browser.plist to browser_backup.plist to backup it
5. Launch Sourcetree
6. Add required repositories to Sourcetree
7. Check if issue reproduces now
8. (if required) to restore list of your repositories you will need to quit Sourcetree, and rename browser_backup.plist back to browser.plist

@Raman Sidarakin

Are you sure about it being fixed in v4.2.3? I'm using v4.2.7 (263) but it still occurs for me.

Thanks! I'll update now.

Hi, b94efa11c5e5 .

The version 4.1.3 (239) you are using is pretty old. This issue was fixed in v4.2.3. Could you please try to use the latest Sourcetree version from official Sourcetree website? 

This is still a thing. 4.1.3 (239). M1 Mac.

Years later, this blocking prompt is still a broken janky piece of garbage that locks up the application that you're supposed to be restarting to "fix" the issue you won't fix.

I'm seeing this on OSX 11.4

The dialog just keeps coming and coming. I can't terminate from the dock.

I had to find the process in Activity Monitor and force quit.