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

Quick Open performance regression #74349

Closed
raiskila opened this issue May 26, 2019 · 2 comments
Closed

Quick Open performance regression #74349

raiskila opened this issue May 26, 2019 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@raiskila
Copy link

  • VSCode Version: 1.34.20-insider, 1.35.0-insider
  • OS Version: macOS 10.14.5 (18F132)

Steps to Reproduce:

  1. git clone git@github.com:facebook/react.git
  2. /Applications/Visual\ Studio\ Code\ -\ Insiders.app/Contents/Resources/app/bin/code --disable-extensions --user-data-dir /tmp/a-new-directory react
  3. Press +P and type a word, say "create".
  4. Observe how quickly the file list populates.

Expected Behavior

The quick open file list populates fast. Recording from 1.34.0-insider:

1.34.0-insider

Actual Behavior

The quick open file list only populates after a delay after you stop typing. Running "Clear Editor History" seems to make the next invocation of Quick Open work faster, but the slowness returns. Recording from 1.34.20-insider:

1.34.20-insider

I think I was able to isolate this to a difference between 1.34.0-insider and 1.34.20-insider. However, I had some trouble getting VSCode to honor the --user-data-dir flag, and it seemed to be partially using the "~/Library/Application Support/Code - insiders" directory until I deleted it.

@bpasero bpasero self-assigned this May 26, 2019
@bpasero bpasero added the bug Issue identified by VS Code Team member as probable bug label May 26, 2019
@bpasero
Copy link
Member

bpasero commented May 26, 2019

Yeah this is on me and should be fixed with 0c53423

Please try on Monday and report back if it is OK for you then, thanks.

@bpasero bpasero closed this as completed May 26, 2019
@bpasero bpasero added this to the May 2019 milestone May 26, 2019
@lramos15 lramos15 added the verified Verification succeeded label May 30, 2019
@raiskila
Copy link
Author

raiskila commented Jun 9, 2019

The issue is gone after updating to 1.36.0-insider. Thanks!

@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants