You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the last release (v0.0.1-Beta3) when errors appear in the console (using WARN debug) then the CPU goes up to 100%.
I suggest to close the thread/tunnel/connection when a fatal error appears in the protocol (that is not when a simple error in the messages appears, but when is connection fails).
This is the full log (warn level) over the last lines... Two comments:
This is with the last release, so if you use the last commit perhaps the problem is solved.
These messages appear when the client initiates a lot of connections (is a web proxy), and when some of these connections are killed (not closed)... Or this is I think! When I use only one connection (for example with a SSH tunnel over the gota multi-link) I don't see any trouble. Even if I redirect the same proxy connection over the SSH tunnel. So, I imagine that the trouble is with not-well-closed sockets.
In any case, I can prepare a more extensive log.
However, please, I suggest that you implement the function #8. This will simplifies the testing as I can tunnel two sockets: one to the webserver and one to the SSH server.
Thanks to you!
lars18th
changed the title
BUG: Performance issue
[BUG] Performance issue
Aug 31, 2017
Hi,
With the last release (v0.0.1-Beta3) when errors appear in the console (using WARN debug) then the CPU goes up to 100%.
I suggest to close the thread/tunnel/connection when a fatal error appears in the protocol (that is not when a simple error in the messages appears, but when is connection fails).
Here the client log when the CPU is at 100%:
I hope this helps.
The text was updated successfully, but these errors were encountered: