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

Closing the wterminal without quitting helix using :q leaves pylyzer running in the background. #12628

Open
V0idLord opened this issue Jan 21, 2025 · 0 comments
Labels
C-bug Category: This is a bug

Comments

@V0idLord
Copy link

Summary

I noticed today that I had pylyzer open in the background, consuming more than 5gb of ram, making me unable to launch a game. Just tested it and closing windows terminal directly without doing :q leaves the pylyzer running in the background and slowly increasing ram usage. I used it with python uv package manager, as such I use ´uv run hx hello.py´ to edit code with the .venv of my project. I apologize in case its not a helix issue and please direct me where I need to report it. I took language.toml configurations from helix documentation here on github.

Reproduction Steps

I tried this:

  1. ´uv run hx hello.py´
  2. close terminal by using X button

I expected this to happen:
helix and related processes are terminated.

Instead, this happened:
pylyzer.exe keeps running and slowly using up all ram

Helix log

No response

Platform

Windows

Terminal Emulator

Windows Terminal

Installation Method

winget

Helix Version

helix 25.01

@V0idLord V0idLord added the C-bug Category: This is a bug label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug
Projects
None yet
Development

No branches or pull requests

1 participant