Git extension is super slow since version 1.56.0 #718

mlbiche · 2021-05-10T13:05:34Z

Describe the bug

Since VSCodium updated to 1.56.0, I am suffering important slowdown of the editor. The SCM is particularly slow in all its features (especially showing diffs and refreshing changes, but also committing). It also causes slowdown for the GitLens extension but the slowdown remain even when disabling the extension. I have run an extension audit and it has shown that Git extension was some time not responsive. It causes slowdown in the whole application, with a kind of side effect on other extensions such as ESLint or Prettier.

I have downgraded VSCodium to the version 1.55.2 and everything is running smoothly then. Upgrading back to 1.56 show the slowdown again?

Please confirm that this problem is VSCodium-specific

This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium. I have tried it on the same project with Visual Studio Code 1.56.

Please confirm that the issue/resolution isn't already documented

I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

Open a project with a remote
Write down some edits.
Open the SCM tab. It should be loading for while
Click a changed file, the diff should takes a while to show up.

Expected behavior
A SCM as fas as it as in the version 1.55.2.

Screenshots

Desktop (please complete the following information):

OS: Mac OS
Architecture x64
Version 1.56.0

paulcarroty · 2021-05-10T16:07:15Z

Can't reproduce it on Linux.

Doable149 · 2021-05-11T15:56:04Z

Same problem on my MacBook Pro 2019, there are errors in the console when i try to add a file to my index :

mainThreadExtensionService.ts:62 TypeError: Cannot read property 'document' of undefined
	at /Users/owen/.vscode-oss/extensions/arjun.swagger-viewer-3.0.1/out/preview/client.js:167
	at fire (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:57)
	at i.$acceptModelChanged (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:87)
	at l._doInvokeHandler (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:91)
	at l._invokeHandler (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:91)
	at l._receiveRequest (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:91)
	at l._receiveOneMessage (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:91)
	at /Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:91
	at fire (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:57)
	at S.fire (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:65)
	at /Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:106
	at fire (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:57)
	at S.fire (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:65)
	at t._receiveMessage (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:65)
	at /Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:65
	at fire (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:57)
	at acceptChunk (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:65)
	at /Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:65
	at Socket.v (/Applications/VSCodium.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:106)
	at Socket.emit (events.js:315)
	at addChunk (internal/streams/readable.js:309)
	at readableAddChunk (internal/streams/readable.js:284)
	at Socket.Readable.push (internal/streams/readable.js:223)
	at Pipe.onStreamRead (internal/stream_base_commons.js:188)
$onExtensionRuntimeError @ mainThreadExtensionService.ts:62
_doInvokeHandler @ rpcProtocol.ts:417
_invokeHandler @ rpcProtocol.ts:402
_receiveRequest @ rpcProtocol.ts:318
_receiveOneMessage @ rpcProtocol.ts:245
(anonymous) @ rpcProtocol.ts:110
fire @ event.ts:622
fire @ ipc.net.ts:468
_receiveMessage @ ipc.net.ts:821
(anonymous) @ ipc.net.ts:660
fire @ event.ts:622
acceptChunk @ ipc.net.ts:241
(anonymous) @ ipc.net.ts:202
_ @ ipc.net.ts:50
emit @ events.js:315
addChunk @ internal/streams/readable.js:309
readableAddChunk @ internal/streams/readable.js:284
Readable.push @ internal/streams/readable.js:223
onStreamRead @ internal/stream_base_commons.js:188

and

[[object Object]]Cannot read property 'document' of undefined
$onExtensionRuntimeError @ mainThreadExtensionService.ts:61
_doInvokeHandler @ rpcProtocol.ts:417
_invokeHandler @ rpcProtocol.ts:402
_receiveRequest @ rpcProtocol.ts:318
_receiveOneMessage @ rpcProtocol.ts:245
(anonymous) @ rpcProtocol.ts:110
fire @ event.ts:622
fire @ ipc.net.ts:468
_receiveMessage @ ipc.net.ts:821
(anonymous) @ ipc.net.ts:660
fire @ event.ts:622
acceptChunk @ ipc.net.ts:241
(anonymous) @ ipc.net.ts:202
_ @ ipc.net.ts:50
emit @ events.js:315
addChunk @ internal/streams/readable.js:309
readableAddChunk @ internal/streams/readable.js:284
Readable.push @ internal/streams/readable.js:223
onStreamRead @ internal/stream_base_commons.js:188

daiyam · 2021-05-11T17:25:27Z

I've done a quick check of the source code of the extension. It might be an issue with the extension.
At line 146-147, there is a check if there is an active editor. Then at line 194, there is no checks.
This might not be the issue but the error log seems to match.

Doable149 · 2021-05-12T09:22:17Z

@daiyam If it is the extension that does this problem do we have the same problem on Visual Studio Code and not only Vscodium ?

daiyam · 2021-05-12T09:30:32Z

@Nopraz Good question. Can you check if you are getting the errors on VSCode even if it's not slow?

Doable149 · 2021-05-12T13:04:44Z

Just checked, no errors on visual studio code

mlbiche · 2021-05-12T15:16:02Z

I have also checked on VSCode the other day and have not seen any slowdown.

daiyam · 2021-05-12T19:16:34Z

I can't reproduce the error with VSCodium v1.56.1 and the examples from the OpenAPI Specification.
Can you give me example of the files on which you are getting the errors? Or try those examples?

robinloeffel · 2021-05-14T07:29:55Z

It's slowed down everywhere—even when just opening up a tiny project I'll see "Initializing JS/TS language features..." and "Activating language features..." spinning in my status bar for what feels like 5 seconds each. It's gotten significantly better for me with v1.56.2, but it's still not where v1.55.2 was. I notice it most when Git pulling (via the UI) and when the autofix feature enabled via editor.codeActionsOnSave.source.fixAll is working.

MrOggy85 · 2021-05-19T06:29:41Z

I have the same issue:
MacBook Pro
MacOs Big Sur, 11.3

$ uname -a
Darwin (HOSTNAME) 20.4.0 Darwin Kernel Version 20.4.0: Fri Mar  5 01:14:14 PST 2021; root:xnu-7195.101.1~3/RELEASE_X86_64 x86_64

Not sure if it's related but here is also my git version:

$ git --version
git version 2.29.0

I just downloaded and installed 1.55.2 and the issue is gone

sagolubev · 2021-05-19T12:08:57Z

I faced the same issue:
Mb Pro 2018, Big Sur 11.3.1
$ uname -a Darwin (HOSTNAME) 20.4.0 Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:47 PDT 2021; root:xnu-7195.101.2~1/RELEASE_X86_64 x86_64
Git:
$ git --version
git version 2.31.1

daiyam · 2021-05-19T13:54:30Z

@mlbiche @MrOggy85 @sagolubev Can you troubleshoot your setup? I'm on macOS and I can't reproduce the issue. I've opened the vscode project with gitlens activated and I don't have any slow down.
Can you try a blank VSCodium with just gitlens activated?

Does the solution of @robinloeffel is working?

{
  "editor.codeActionsOnSave": {
    "source.fixAll": true
  }
}

MrOggy85 · 2021-05-19T14:42:04Z

@daiyam I tried it, but no difference.
I have Gitlens extension installed but I also tried to disabled it but no difference.
I also disabled all extensions, but no difference.
I also removed all my settings, but no difference.

It happens for any type of files. I have tried with .ts, .json, .md
It happens both if I open a folder and if I use workspace (which is even slower).

daiyam · 2021-05-19T14:55:28Z

Can you edit /Applications/VSCodium.app/Contents/Resources/app/product.json and replace "extensionAllowedProposedApi": [...], with the following code?

"extensionAllowedProposedApi": ["GitHub.codespaces", "GitHub.vscode-pull-request-github-insiders", "GitHub.vscode-pull-request-github", "Microsoft.vscode-nmake-tools", "ms-ai-tools.notebook-renderers", "ms-dotnettools.dotnet-interactive-vscode", "ms-python.gather", "ms-python.python", "ms-toolsai.jupyter", "ms-toolsai.vscode-ai", "ms-toolsai.vscode-ai-remote", "ms-vscode-remote.remote-containers-nightly", "ms-vscode-remote.remote-containers", "ms-vscode-remote.remote-ssh-edit-nightly", "ms-vscode-remote.remote-ssh-edit", "ms-vscode-remote.remote-ssh-nightly", "ms-vscode-remote.remote-ssh", "ms-vscode-remote.remote-wsl-nightly", "ms-vscode-remote.remote-wsl", "ms-vscode-remote.remote-wsl-recommender", "ms-vscode-remote.vscode-remote-extensionpack-nightly", "ms-vscode-remote.vscode-remote-extensionpack", "ms-vscode.azure-account", "ms-vscode.azure-sphere-tools-ui", "ms-vscode.azure-sphere-tools", "ms-vscode.github-browser", "ms-vscode.github-richnav", "ms-vscode.remotehub", "ms-vscode.remotehub-insiders", "ms-vscode.js-debug-nightly", "ms-vscode.js-debug", "ms-vscode.lsif-browser", "ms-vscode.vscode-js-profile-flame", "ms-vscode.vscode-js-profile-table", "ms-vscode.vscode-selfhost-test-provider", "ms-vscode.test-adapter-converter", "ms-vsliveshare.cloudenv-explorer", "ms-vsliveshare.cloudenv", "ms-vsliveshare.vsliveshare", "ms-vsonline.vsonline", "dbaeumer.vscode-eslint"],

MrOggy85 · 2021-05-19T15:02:26Z

I tried it, but still no difference

MrOggy85 · 2021-05-19T15:08:16Z

I also tried removing the app and install the latest version from the .dmg file from "Releases" page here on Github.
But, still same issue.

Originally I installed vscodium from brew, if that helps at all.

daiyam · 2021-05-19T15:55:55Z

I've looked at the git extension and I've seen that vscode's team have added virtual workspaces. So the change of extensionAllowedProposedApi was related to that. Maybe it's another property of product.json that needs to be updated, but I don't know...

d11-acummins · 2021-06-18T10:34:36Z

This still occurs on latest. Also tried disabling all extensions, but no luck

OS: macOS 11.2.3
Architecture x64
Version 1.57.1

MrAlexWeber · 2021-07-01T19:00:48Z

I was able to confirm that downgrading to 1.55.2 fixed my issue with laggy editor behavior when switching tabs or opening files.

daiyam · 2021-07-01T22:15:29Z

Was it from local files or remote files?

stripedpajamas · 2021-07-02T16:46:54Z

I was also able to reproduce this issue on my mac with versions >1.55.2. The whole editor became noticibly sluggish. I'll keep poking at it to see if I can figure out what changed.

daiyam · 2021-07-02T17:30:11Z

While playing with remote ssh, I found that I can't connect to my VM with VSCodium where I can with VSCode...

MrAlexWeber · 2021-07-02T21:34:46Z

For me, local files.

…

On Thu, Jul 1, 2021 at 15:15 Baptiste Augrain ***@***.***> wrote: Was it from local files or remote files? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#718 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADRE3IM56EOKYIWZVWUOCDTVTSIZANCNFSM44REVNNQ> .

Until VSCodium git extension bug is fixed (VSCodium/vscodium#718).

atapfedora · 2021-07-07T15:40:27Z

Same here in Manjaro, I tried to install python extension on Vscodium, but it keeps "installing" and nothing happens

enx1998 · 2021-07-09T08:20:54Z

Hi,
I have the same problem with 1.57.1 version and macos 11.4 on a macbook pro 16".
I add that the extension doesn't work (it doesn't recognize the git repository) until I disable and enable it again.

daiyam · 2021-07-09T09:37:46Z

@atapfedora @enx1998 If you are talking about the python extension, please open another issue. This issue is about slow git...

daiyam · 2021-07-09T09:40:09Z

For the git issue, I can't reproduce it on my macOS or my arch linux... VSCode is having the same issue (for example: microsoft/vscode#120883)

Can you share your git --version and the Git log in View/Output?

Nesh108 · 2022-03-28T11:30:33Z

Any update on the issue? I'd love to update sooner or later 😅

brkn · 2022-03-28T13:11:56Z

I'm on version

1.65.1
8908a9ca0f221f36507231afb39d2d8d1e182702
x64

Git speed is back to normal for me.

[2022-03-28T14:50:17.697Z] > git symbolic-ref --short HEAD [3ms]
[2022-03-28T14:50:17.793Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track) refs/heads/fix/monetary-columns refs/remotes/fix/monetary-columns [4ms]
[2022-03-28T14:50:17.963Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [84ms]
[2022-03-28T14:50:17.964Z] > git remote --verbose [5ms]
[2022-03-28T14:50:18.050Z] > git config --get commit.template [5ms]
[2022-03-28T14:50:22.190Z] > git ls-tree -l HEAD -- /path/package.json [6ms]

eloo · 2022-03-28T13:28:27Z

for me its still super slow :(

[2022-03-28T13:26:54.297Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [806ms]
[2022-03-28T13:26:56.684Z] > git ls-files --stage -- /Users/... [1182ms]
[2022-03-28T13:26:57.077Z] > git config --get commit.template [1976ms]
[2022-03-28T13:26:57.479Z] > git cat-file -s ... [402ms]

Version: 1.64.2
Commit: f80445acd5a3dadef24aa209168452a3d97cc326
Date: 2022-02-09T22:00:58.347Z (1 mo ago)
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 20.6.0

and since it looks like nobody is trying to fix this i will switch back to vscode...

robrecord · 2022-03-28T13:51:12Z

[2022-03-28T13:26:57.479Z] > git cat-file -s ... [402ms]

~~Do you mind telling us how to output these benchmarks?~~

Nevermind, I see now - Panel > Output > git

dandavison · 2022-03-28T13:53:03Z

Note that this doesn't seem to be a VSCodium problem -- it seems to be a problem with open source builds of VSCode in general (see my notes above: #718 (comment)). So that's good in a way, because the problem is relevant to a much larger set of people and we can seek advice/explanation from anyone familiar with building VSCode; we should probably open an issue on the main VSCode repo (although we should check it's still occurring with the latest release).

robrecord · 2022-03-28T14:01:36Z

A comparison on my machine. Same (symlinked) plugins and settings files. I installed these via brew and did not build them from source.

VS Codium

Version: 1.65.2
Commit: c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1
Date: 2022-03-11T00:39:29.134Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 21.3.0

Git output:

[2022-03-28T13:52:52.144Z] > git remote --verbose [2766ms]
[2022-03-28T13:52:52.628Z] > git ls-files --stage --  .../package.json [1882ms]
[2022-03-28T13:52:54.013Z] > git cat-file -s 375bb320bdabb871dc602f8ff7715d99b1ce90ca [956ms]
[2022-03-28T13:52:54.016Z] > git config --get commit.template [1398ms]
[2022-03-28T13:52:54.930Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [1388ms]

VSCode

Version: 1.65.2
Commit: c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1
Date: 2022-03-10T14:33:49.188Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 21.3.0

Git output:

[2022-03-28T13:58:51.076Z] > git remote --verbose [7ms]
[2022-03-28T13:58:27.678Z] > git ls-files --stage -- .../package.json [7ms]
[2022-03-28T13:58:27.684Z] > git cat-file -s 375bb320bdabb871dc602f8ff7715d99b1ce90ca [6ms]
[2022-03-28T13:58:51.088Z] > git config --get commit.template [7ms]
[2022-03-28T13:58:51.077Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [10ms]

In a table

	VS Codium	VS Code
Version	1.65.2	1.65.2
Commit	c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1	c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1
Date	2022-03-11T00:39:29.134Z	2022-03-10T14:33:49.188Z
Electron	13.5.2	13.5.2
Chromium	91.0.4472.164	91.0.4472.164
Node.js	14.16.0	14.16.0
V8	9.1.269.39-electron.0	9.1.269.39-electron.0
OS	Darwin x64 21.3.0	Darwin x64 21.3.0

	VS Codium	VS Code
git remote --verbose	2766ms	7ms
git ls-files --stage -- .../package.json	1882ms	7ms
git cat-file -s 375bb320bdabb871dc602f8ff7715d99b1ce90ca	956ms	6ms
git config --get commit.template	1398ms	7ms
git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname)	1388ms	10ms

mlbiche · 2022-03-28T14:06:32Z

I am experiencing the same latency even if it feels a bit better than before. It is almost usable.

@dandavison When I was first searching for fixes for this issue, I found some issues on VSCode repository but the only solution mentioned was to remove Codesign signatures which does not solve the slowness on my machine.

@brkn Can you post the output you have in Panel > Output > Git as they did please ?

dandavison · 2022-03-28T14:14:48Z

@robrecord can you characterize the git repo you're testing in -- many files? many branches/tags? etc I was testing in a very large monorepo with many branches and tags.

robrecord · 2022-03-28T16:11:40Z

@robrecord can you characterize the git repo you're testing in -- many files? many branches/tags? etc I was testing in a very large monorepo with many branches and tags.

A monorepo with a large amount of files, but few branches and tags (4 local branches, 3 remote branches, one remote, no tags), about a hundred commits.

gabjauf · 2022-03-29T10:35:39Z

Hey guys,

The observations I made on my side:

Both VSCodium and VSCode have the issue
I get 100% CPU usage process by Electron times the number of windows of VSCodium opened
Stopping the "Electron" process causes the vscode.git extension to crash
On startup, it takes a lot of time to load because of vscode.git (UNRESPONSIVE)
During normal usage, git extension is slow, whatever is the repository I use
It is happening on Mac, not linux (according to the comments)

My configuration:

Version: 1.65.2
Commit: c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1
Date: 2022-03-11T00:39:29.134Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 21.3.0

Useful comments:
"I assume this unexplained timing difference is related to the cursor movement UI performance problem that is the real issue here" #718 (comment)

@dandavison You said that "it seems to be a problem with open source builds of VSCode in general", do you have any issue referencing the same kind of issue in other open source builds of VSCode?

Edit: corrected the fact that VSCode seems to be also affected by this issue

dandavison · 2022-03-29T10:51:58Z

@dandavison You said that "it seems to be a problem with open source builds of VSCode in general", do you have any issue referencing the same kind of issue in other open source builds of VSCode?

Yes - the problems with the git extension performance that I reported above, and the timings, none of it used VSCodium in any way (in fact I've never used VSCodium). Everything I did was using OSS builds of vanilla VSCode on MacOS.

daiyam · 2022-03-29T11:15:32Z

VSCodium has the issue, not VSCode

To be clear, even some users of VSCode have the same issue.

mlbiche · 2022-03-29T12:48:37Z

Some issues on VSCode repository :

angwe · 2022-04-20T16:46:45Z

Cropping back up on my macOS Monterey machine with VSCodium 1.66.2

Recent happening too, it wasn't occurring with earlier versions.

Most noticeable in the intersection between completion plug-ins (which suddenly hang and stall the cursor) and built-in git. Sometimes GitLens is trying to do something, but most of the time, it's just the background git process checking for updates.

Added - sometimes there is no completion happening, the cursor just stalls. It's a full UI freeze, I just seem to notice it more when a completion is trying to run.

robrecord · 2022-04-21T13:44:26Z

The only thing I can think of is that it's something to do with the compiler used.

gabjauf · 2022-04-22T08:41:37Z

profile.json.zip

Found a CPU profile in the developer tools, if it can help 😉

daiyam · 2022-04-27T16:28:45Z

Hi, for those on M1, you might want to try the new arm64 binary.

TheOnlyDasBoot · 2022-05-03T13:42:38Z

Visual Studio 2019 v16.11.12 - If I am attached to the internet GitHub turns my pc into a turtle. Disconnect internet and pc is the hare.

Also working in a project that is not associated with GitHub with internet connection works just fine.

GitHub is the problem here.

Nesh108 · 2022-05-03T13:46:32Z

@TheOnlyDasBoot here we are discussing how to fix a slowdown on VsCodium, not whining about GitHub. Make a new issue on https://github.com/github

daiyam · 2022-05-03T13:53:03Z

@TheOnlyDasBoot Your issue isn't related to VSCodium so please avoid any further ranting here. Thx

mlbiche · 2022-05-10T10:24:28Z

I have updated VSCodium to version 1.67.0 and tried to enable the Git extension again and it seems to run smoother, even with GitLens enabled. I haven't tested on previous VSCodium versions so I don't know if the fix comes from the last version. Here is my Git output today :

[2022-05-10T10:20:02.333Z] > git rev-parse --show-toplevel [10ms]
[2022-05-10T10:20:02.387Z] > git rev-parse --git-dir --git-common-dir [48ms]
[2022-05-10T10:20:02.392Z] Open repository: /...
[2022-05-10T10:20:02.416Z] > git status -z -uall [19ms]
[2022-05-10T10:20:02.433Z] > git symbolic-ref --short HEAD [15ms]
[2022-05-10T10:20:02.451Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/67-champ-obligatoire refs/remotes/67-champ-obligatoire [16ms]
[2022-05-10T10:20:02.650Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [196ms]
[2022-05-10T10:20:02.651Z] > git remote --verbose [196ms]
[2022-05-10T10:20:02.777Z] > git config --get commit.template [66ms]
[2022-05-10T10:20:03.160Z] > git show --textconv :CHANGELOG.md [139ms]
[2022-05-10T10:20:03.178Z] > git ls-files --stage -- /.../CHANGELOG.md [155ms]
[2022-05-10T10:20:03.395Z] > git cat-file -s 3a74f319c452df8e99db2ca704ab30f463cd77ef [214ms]
[2022-05-10T10:20:03.402Z] > git check-ignore -v -z --stdin [12ms]

Some commands still take longer than 100ms on VSCodium startup, but none are afterward.

🎉

eloo · 2022-05-10T13:59:38Z

Can confirm with the new version it seems to be better

enx1998 · 2022-05-11T10:18:31Z

Hi all,
I have installed the 1.67.1 version and I can no longer get the git extension to work: appears to be installed and enabled, but when I open the git panel appears the following sentence:
If you would like to use git features, please enable git in your settings
and in settings there is no git setting to change.
If I disable the Git (built-in) extension and after a reload of vscodium, I enable it again it appears to work, but when I restart vscodium it stops working, showing the sentence above.

jeffery9 · 2022-08-04T08:44:56Z

git status is very slow.

[2022-08-04T08:34:58.625Z] > git cat-file -s 92cf8c1633f3687b4d266f001a36fbd7af6688a3 [45ms]
[2022-08-04T08:35:33.889Z] > git status -z -uall [84556ms]
[2022-08-04T08:35:33.932Z] > git symbolic-ref --short HEAD [20ms]
[2022-08-04T08:35:34.015Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/zll-test refs/remotes/zll-test [62ms]
[2022-08-04T08:35:34.074Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [37ms]
[2022-08-04T08:35:34.081Z] > git remote --verbose [22ms]
[2022-08-04T08:35:34.111Z] > git config --get commit.template [10ms]
[2022-08-04T08:36:01.072Z] > git rev-parse --show-toplevel [46ms]

vscode version

Version: 1.69.2
Commit: 3b889b090b5ad5793f524b5d1d39fda662b96a2a
Date: 2022-07-18T16:12:57.074Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Darwin x64 21.6.0

MatthiasPortzel · 2022-08-14T21:30:06Z

I upgraded from 1.66 to 1.70 today and Git performance is much better! This issue is solved as far as I'm concerned.

github-actions · 2023-02-11T01:33:31Z

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!

github-actions · 2023-03-14T01:31:38Z

This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue, please open a new issue.

mlbiche added the bug Something isn't working label May 10, 2021

MrAlexWeber mentioned this issue Jul 1, 2021

Extension issue: vscode.git high usage, maybe blocking interaction on file load microsoft/vscode#127809

Closed

TyMick added a commit to TyMick/ohmyzsh-custom that referenced this issue Jul 6, 2021

Temporarily switch to VS Code

4c4ab68

Until VSCodium git extension bug is fixed (VSCodium/vscodium#718).

github-actions bot added the stale label Feb 11, 2023

github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 14, 2023

github-actions bot locked as resolved and limited conversation to collaborators Jun 12, 2023

Git extension is super slow since version 1.56.0 #718

Git extension is super slow since version 1.56.0 #718

Comments

mlbiche commented May 10, 2021

paulcarroty commented May 10, 2021

Doable149 commented May 11, 2021

daiyam commented May 11, 2021

Doable149 commented May 12, 2021

daiyam commented May 12, 2021

Doable149 commented May 12, 2021

mlbiche commented May 12, 2021

daiyam commented May 12, 2021

robinloeffel commented May 14, 2021

MrOggy85 commented May 19, 2021 • edited

sagolubev commented May 19, 2021

daiyam commented May 19, 2021 • edited

MrOggy85 commented May 19, 2021

daiyam commented May 19, 2021

MrOggy85 commented May 19, 2021

MrOggy85 commented May 19, 2021

daiyam commented May 19, 2021

d11-acummins commented Jun 18, 2021

MrAlexWeber commented Jul 1, 2021

daiyam commented Jul 1, 2021

stripedpajamas commented Jul 2, 2021

daiyam commented Jul 2, 2021

MrAlexWeber commented Jul 2, 2021 via email

atapfedora commented Jul 7, 2021

enx1998 commented Jul 9, 2021

daiyam commented Jul 9, 2021

daiyam commented Jul 9, 2021

Nesh108 commented Mar 28, 2022

brkn commented Mar 28, 2022 • edited

eloo commented Mar 28, 2022

robrecord commented Mar 28, 2022 • edited

dandavison commented Mar 28, 2022

robrecord commented Mar 28, 2022 • edited

VS Codium

VSCode

In a table

mlbiche commented Mar 28, 2022 • edited

dandavison commented Mar 28, 2022

robrecord commented Mar 28, 2022 • edited

gabjauf commented Mar 29, 2022 • edited

dandavison commented Mar 29, 2022

daiyam commented Mar 29, 2022

mlbiche commented Mar 29, 2022

angwe commented Apr 20, 2022 • edited

robrecord commented Apr 21, 2022

gabjauf commented Apr 22, 2022 • edited

daiyam commented Apr 27, 2022

TheOnlyDasBoot commented May 3, 2022 • edited

Nesh108 commented May 3, 2022

daiyam commented May 3, 2022

mlbiche commented May 10, 2022

eloo commented May 10, 2022

enx1998 commented May 11, 2022

jeffery9 commented Aug 4, 2022

MatthiasPortzel commented Aug 14, 2022 • edited

github-actions bot commented Feb 11, 2023

github-actions bot commented Mar 14, 2023

MrOggy85 commented May 19, 2021 •

edited

daiyam commented May 19, 2021 •

edited

brkn commented Mar 28, 2022 •

edited

robrecord commented Mar 28, 2022 •

edited

robrecord commented Mar 28, 2022 •

edited

mlbiche commented Mar 28, 2022 •

edited

robrecord commented Mar 28, 2022 •

edited

gabjauf commented Mar 29, 2022 •

edited

angwe commented Apr 20, 2022 •

edited

gabjauf commented Apr 22, 2022 •

edited

TheOnlyDasBoot commented May 3, 2022 •

edited

MatthiasPortzel commented Aug 14, 2022 •

edited