-
Notifications
You must be signed in to change notification settings - Fork 419
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 after transport error. #29
Comments
The problem is here It seems it gets called twice as result it tries to destroy already destroyed socket. You might try to comment line |
I have found the problem NTCPSession::Send produces async_write while termination event is pending. Will fix it. |
Supposed to be fixed now |
I will try to recreate the error. It usually happens if I let it run for some hours. |
Hmm, still crashes, but now it's the Log object.
|
Lol. That's what it is |
Ok, I can do that one. Better if you do the async or some other task that is currently too heavy for me :) |
I've seen this error sometimes now, finally I catched it while running in gdb.
Unsure where to go from here, but it seems to happen because of an unexpected close of transport.
The text was updated successfully, but these errors were encountered: