-
Notifications
You must be signed in to change notification settings - Fork 946
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
Connector::Cancel crash #9
Labels
Comments
zieckey
added a commit
that referenced
this issue
Mar 17, 2017
When TCPClient is connecting to a host and it is doing a DNS resolving, the user calls TCPClient::Disconnect, that will cause a crush at Connector::Cancel::chan_->DisableAllEvent() void Connector::Cancel() { LOG_INFO << "Cancel to connect " << remote_addr_ << " status=" << StatusToString(); assert(loop_->IsInLoopThread()); if (dns_resolver_) { dns_resolver_->Cancel(); } assert(timer_); timer_->Cancel(); chan_->DisableAllEvent(); chan_->Close(); }
fixed |
zieckey
added a commit
that referenced
this issue
Mar 25, 2017
When TCPClient is connecting to a host and it is doing a DNS resolving, the user calls TCPClient::Disconnect, that will cause a crush at Connector::Cancel::chan_->DisableAllEvent() void Connector::Cancel() { LOG_INFO << "Cancel to connect " << remote_addr_ << " status=" << StatusToString(); assert(loop_->IsInLoopThread()); if (dns_resolver_) { dns_resolver_->Cancel(); } assert(timer_); timer_->Cancel(); chan_->DisableAllEvent(); chan_->Close(); }
zieckey
added a commit
that referenced
this issue
Apr 27, 2017
When TCPClient is connecting to a host and it is doing a DNS resolving, the user calls TCPClient::Disconnect, that will cause a crush at Connector::Cancel::chan_->DisableAllEvent() void Connector::Cancel() { LOG_INFO << "Cancel to connect " << remote_addr_ << " status=" << StatusToString(); assert(loop_->IsInLoopThread()); if (dns_resolver_) { dns_resolver_->Cancel(); } assert(timer_); timer_->Cancel(); chan_->DisableAllEvent(); chan_->Close(); }
zieckey
added a commit
that referenced
this issue
May 20, 2017
When TCPClient is connecting to a host and it is doing a DNS resolving, the user calls TCPClient::Disconnect, that will cause a crush at Connector::Cancel::chan_->DisableAllEvent() void Connector::Cancel() { LOG_INFO << "Cancel to connect " << remote_addr_ << " status=" << StatusToString(); assert(loop_->IsInLoopThread()); if (dns_resolver_) { dns_resolver_->Cancel(); } assert(timer_); timer_->Cancel(); chan_->DisableAllEvent(); chan_->Close(); }
zieckey
added a commit
that referenced
this issue
May 20, 2017
When TCPClient is connecting to a host and it is doing a DNS resolving, the user calls TCPClient::Disconnect, that will cause a crush at Connector::Cancel::chan_->DisableAllEvent() void Connector::Cancel() { LOG_INFO << "Cancel to connect " << remote_addr_ << " status=" << StatusToString(); assert(loop_->IsInLoopThread()); if (dns_resolver_) { dns_resolver_->Cancel(); } assert(timer_); timer_->Cancel(); chan_->DisableAllEvent(); chan_->Close(); }
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When TCPClient is connecting to a host and it is doing a DNS resolving, the user calls TCPClient::Disconnect, that will cause a crush at Connector::Cancel::chan_->DisableAllEvent()
The text was updated successfully, but these errors were encountered: