Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension becomes a CPU hog #3307

Open
vthemelis opened this issue May 19, 2024 · 2 comments
Open

Extension becomes a CPU hog #3307

vthemelis opened this issue May 19, 2024 · 2 comments
Labels
bug Something isn't working triage Needs to be looked at

Comments

@vthemelis
Copy link

Description

The extension calls git commands that can take a very long time (eg more than a day) and keep them running. This shows as a large amount of git processes running on the background each using 100% of the CPU.

Could we add timeouts to these?

What triggered this for me was checking out a huge repo with a tree filter and then blaming a file:

# Clone huge repository with a filter
git clone --filter tree:0 https://github.com/DefinitelyTyped/DefinitelyTyped

and then blame a few files with the extension to reproduce.

Can we add a timeout to git commands?

GitLens Version

15.0.3

VS Code Version

No response

Git Version

No response

Logs, Screenshots, Screen Captures, etc

No response

@vthemelis vthemelis added bug Something isn't working triage Needs to be looked at labels May 19, 2024
@xrstf
Copy link

xrstf commented Sep 5, 2024

I am also experiencing issues with GitLens. At first I blamed microsoft/vscode#213136, but after disabling GitLens, the CPU usage immediately went down.

However, running strace on the evil process does not show it spawning tons of git processes, so I really do not know why GitLens has been frying my CPU for nearly half a year now (until I figured out, today, that it is the culprit).

@vthemelis
Copy link
Author

The issue is not that it keeps on spacing processes. The issue is that at since point it so prawns processes that stay running for a very long time. For me it was obvious by looking on the output of ps aux

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Needs to be looked at
Projects
None yet
Development

No branches or pull requests

2 participants