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

High CPU load after batch replacing hundreds of strings inside a workspace #266

Open
6 tasks
noisnemid opened this issue Jan 24, 2021 · 1 comment
Open
6 tasks

Comments

@noisnemid
Copy link
Contributor

noisnemid commented Jan 24, 2021

Please follow the troubleshooting guide to locate the culprit.

If troubleshooting does not reveal any useful information, provide the following information to create a new issue,

Environment

  • Extension version: 141.0
  • Visual Studio Code version: Code OSS on Archlinux, 1.52.1
  • Operating System version: Archlinux, latest.
  • Python version: 3.9.1
  • sphinx version: 3.4.3
  • A sample of conf.py or its important fragments:

Expected behavior
i think the software should do nothing after batch replacing.
at least do not check the files as soon as they are doing some string-replaceing operations until the user opens it manually, or manually runs a workplace check later.
maybe there could be a switch to turn this operation off.

Actual behavior
The CPU got to 100% load, and the vscode stucks for a long time, then hundreds of erros jumps out in the 'PROBLEMS' panel, most of them are from docutils.

Detailed Steps to reproduce the problem

install vscode

install rst extension only, (or disable all other extensions).

open a rst project with more than 400 docs in it.

ctrl+shift+h, open the batch replacing panel on the side zone, try to repace some string, the the CPU got 100% for more than 2 minus!

enabling or disabling snooty does not make any difference on this issue.

if there's not any extensiong installed and the vscode runs cleanly as a brand new installation, this issue does not occur (the CPU load drops to around 0% as soon as the batch replacing is completed).

@lextm
Copy link
Member

lextm commented Mar 9, 2022

After switching to esbonio, such issues might also be resolved.

Can you upgrade to release 176.0.0 and try again?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants