-
Notifications
You must be signed in to change notification settings - Fork 0
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
Disconnection from testit client can crash server #3
Comments
This behavior is due to improper error handling in the server-side implementation of the ASG API. Fixing the superficial bug, which causes the error code from the failed xm_get to be picked up, the cleanup code causes further issues. Output below.
|
How did you fix the superficial bug? |
It's not committed (because of the "btw" comment), but this is what I did first.
|
It appears that removing aesop threadpools (that were not useful in any event) from batches has fixed the issue. Unrecognized ops will now abort the batches they're included in without segfaulting the server. |
After disconnect, server displays this message, then segfaults:
Expected output varies, but one example of reasonable output is:
This is extremely intermittent.
The text was updated successfully, but these errors were encountered: