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

asyncproc does not expose close procedure #16

Open
seruum opened this issue Dec 28, 2018 · 0 comments · May be fixed by #41
Open

asyncproc does not expose close procedure #16

seruum opened this issue Dec 28, 2018 · 0 comments · May be fixed by #41

Comments

@seruum
Copy link

seruum commented Dec 28, 2018

I am working on a long running process that will start another process using asyncproc. After a couple of days it crashes stating that too many file handles are open. I am suspecting it is because the processes started are not being closed (based on information in osproc). I found the closed procedure in the code, but it is not exported. I didn't want to export it because I thought there might be a reason I'm missing somewhere.

Therefore, why is the close procedure not exported in asyncproc?

Menduist added a commit to Menduist/asynctools that referenced this issue May 19, 2022
@Menduist Menduist linked a pull request May 19, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant