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.

Sign up for GitHub

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

Jump to bottom

High cpu usage by parallel svn processes #463

Closed
stefangraber opened this issue Jan 22, 2019 · 2 comments
Closed

High cpu usage by parallel svn processes #463

stefangraber opened this issue Jan 22, 2019 · 2 comments
Labels
released

Comments

@stefangraber
Copy link

  • VSCode Version: 1.30.2
  • OS Version: Windows 7 Enterprise
  • Extension Version: 1.47.0
  • System Language: german
  • SVN Version:

Issue

I have an ansible project using 18 roles as svn:externals.
VSCode periodically starts a lot of svn processes in parallel causing a high cpu usage.
Changing svn.remoteChanges.checkFrequency to 0 of course is a possible workaround.
But it would be better to limit the number of parallel spawning svn processes.

SVN Output

svn info --xml <external1>
svn info --xml <external2>

Screenshots

vscodeprocesses
CPU-20190122T144540.cpuprofile.txt
@JohnstonCode
Copy link
Owner

Thanks for raising this and looking into the cause.

edgardmessias added a commit to edgardmessias/svn-scm that referenced this issue Mar 26, 2019
@edgardmessias
fix: Fixed high cpu usage by parallel svn processes (close JohnstonCo…
cf07702 
…de#463)
edgardmessias added a commit to edgardmessias/svn-scm that referenced this issue Mar 26, 2019
@edgardmessias
fix: Fixed high cpu usage by parallel svn processes (close JohnstonCo…
118f2de 
…de#463)
JohnstonCode added a commit that referenced this issue Mar 26, 2019
@JohnstonCode
chore(release): 1.47.7 [skip ci]
cd56de4 
## [1.47.7](v1.47.6...v1.47.7) (2019-03-26)

### Bug Fixes

* Fixed high cpu usage by parallel svn processes (close [#463](#463)) ([#531](#531)) ([e70872c](e70872c))
@JohnstonCode
Copy link
Owner

🎉 This issue has been resolved in version 1.47.7 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
released
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stefangraber @JohnstonCode