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

bug: symf not killed when workspace closes or VS Code quits #1877

Closed
toolmantim opened this issue Nov 24, 2023 · 0 comments · Fixed by #2225
Closed

bug: symf not killed when workspace closes or VS Code quits #1877

toolmantim opened this issue Nov 24, 2023 · 0 comments · Fixed by #2225
Assignees
Labels
bug Something isn't working clients/vscode prd-p0

Comments

@toolmantim
Copy link
Contributor

Version

0.16.0

Describe the bug

If a workspace kicks off symf indexing and you close the workspace window, or even quit VS Code altogether, it continues to index in the background. The only way to stop it is to force kill the process in Activity Monitor.

To recreate:

  • Open activity monitor, filtered by 'smyf'
  • Open a large repository (e.g. chromium)
  • See symf indexing
  • Close the workspace and see symf still indexing
  • Quit VS Code and see symf still indexing

Expected behavior

symf is terminated when a workspace is closed and when VS Code quits

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working clients/vscode prd-p0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants