Open icedream opened 8 years ago
After investigating this issue it seems that the TS3 client reports back that its process has been terminated, however it keeps running with the error_report
binary as its child. Conclusion of this is that this is a result of a client crash. The reasons for this are still unknown however the crash seems to happen more often (not always) when the bot is idling for a long time.
Main priority should be for now to get the bot to restart the client properly, avoiding the bind failure by actively terminating all left-over processes by the old client. After that is in place, we can debug further to fix the TeamSpeak3 client crash itself, if possible.
For details, see comments.