Specs:
Issue:
I have tried using older versions and newer versions of SourceTree, and the problem occurs on those versions as well. My Git repositories are working fine on a command line. I have tried searching for others experiencing this same issue, but I have not found any who are.
When I load SourceTree, I am met with a blank tab and the program trying to load from this blank tab. Adding in existing repositories to SourceTree is incredibly slow, taking around ten minutes to add the repository. SourceTree is also very slow in loading the commit history of any repository tab I click. Essentially, performing any action in SourceTree is extremely slow.
In Window's Task Manager, SourceTree uses around 68,000KB of memory around one minute after opening the program. After ten minutes of opening SourceTree, it is using over 500,000KB of memory.
1 minute after opening SourceTree:
10 minutes after opening SourceTree:
Things I have tried:
Please help me!
Hello! I suspect that you're loading in a huge repo (note the 4 git processes running in task manager that have not finished!). To see what's taking so long, could you try the following?
I performed the actions you mentioned. At first, the processes were very quick, each taking less than a second to complete. Then, however, I noticed two processes that never stopped trying to complete. Finally, those processes stopped and new processes began popping up, identical to the previous ones, and these new processes also never stopped trying to complete.
[
{
"Command": "git -c diff.mnemonicprefix=false -c core.quotepath=false status --porcelain --untracked-files=all --ignore-submodules=dirty",
"Directory": "C:\\",
"Status": "Running",
"Duration": "00:00:59.5990000",
"CallerContext": "GetStatusProcess",
"Output": null
},
{
"Command": "git -c diff.mnemonicprefix=false -c core.quotepath=false status --porcelain --ignore-submodules=dirty --untracked-files=all",
"Directory": "C:\\",
"Status": "Running",
"Duration": "00:00:56.5650000",
"CallerContext": "GetFileStatus",
"Output": null
}
]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah ha! Okay, so it looks like the reason why it takes so long is because your entire C:\ drive is a git repository (note how the path is 'C:\')! This means that any file change anywhere on your harddrive will be indexed and monitored by git.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.