If a TLS error occurs, it could end up in a situation where the network handler code did not want to read or write because it only had the error flag set. However, this was not handled, which left the socket triggering in the event loop - but nothing was done to handle it. This can easily cause a 100% cpu situation - the hub is still functioning though while this is happening.pull/75/merge
parent
cff10910ad
commit
35d8088b44
Loading…
Reference in new issue