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

Halting a run after solver is created leaves zombie processes #66

Open
tnelson opened this issue Jan 16, 2021 · 1 comment
Open

Halting a run after solver is created leaves zombie processes #66

tnelson opened this issue Jan 16, 2021 · 1 comment
Labels
bug Something isn't working solver backend

Comments

@tnelson
Copy link
Owner

tnelson commented Jan 16, 2021

Fixing this probably means creating a custodian that kills all runs on termination.
@tnelson
Copy link
Owner Author

tnelson commented Oct 23, 2024

This is much rarer now than in 2021, but I have still seen it happen in debugging contexts. I'm leaving this issue open out of caution, because I want us to take a closer look at it (particularly as we are modernizing the VSCode extension and how we run Forge in general.)

@tnelson tnelson added bug Something isn't working solver backend labels Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working solver backend
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tnelson