-
Notifications
You must be signed in to change notification settings - Fork 25
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
Crash at exit #164
Comments
The scrambled output means that there are many processes here stopped at the same time by SIGINT. |
The graph computations are using a ThreadPool (https://github.com/rwth-i6/sisyphus/blob/master/sisyphus/graph.py#L232C12-L232C12). |
Are you saying I'm not searching for workarounds. Also, I could simply just ignore this message. I simply report this because I think it's bad if the process crashes with |
No, I'm not saying |
I get this now very frequently (I don't remember the last time that Sisyphus quit without this error). Even at normal exit:
Or when interrupting:
|
I looked at bit at the code. There are multiple problems: I assume some background thread is currently iterating through the graph ( This is how the pool was created: self._pool = ThreadPool(gs.GRAPH_WORKER)
atexit.register(self._pool.close) Similarly, the So I guess this atexit handler gets called, then this triggers all the Further, the But then also, the spamming of errors is unnecessary. In all code, before we do any |
Sometimes, but not always (maybe 20% of the cases?), when I hit Ctrl+C, I get this crash:
The text was updated successfully, but these errors were encountered: