[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #3037 [Tor Client]: Internal checks to detect client streams/circuits whose sock request vanished
#3037: Internal checks to detect client streams/circuits whose sock request
vanished
-------------------------+--------------------------------------------------
Reporter: arma | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Tor: 0.2.3.x-final
Component: Tor Client | Version:
Keywords: | Parent:
Points: | Actualpoints:
-------------------------+--------------------------------------------------
Tor has a cycle for handling streams, where it attaches the stream to a
circuit, gives up after a while, attaches it to another, etc.
Tor also has a timeout after which it hangs up on the socks connection,
and some logic to notice that a socks connection has hung up so it should
cancel streams.
Long ago, it was quite common for me to see the "keep trying" cycle
continue even after the socks request had vanished. Those were bugs.
I haven't seen them so much recently, but it would be smart to add some
logic to check the consistency of "for each thing we're trying to handle,
is there still a connection around that's asking us to handle it." If we
had that logic, it might help catch the root cause of #2983.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3037>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs