[tor-bugs] #9862 [Stem]: Tor hangs if you ask it to open too many ORPorts
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Oct 2 19:52:31 UTC 2013
#9862: Tor hangs if you ask it to open too many ORPorts
------------------------+--------------------------------
Reporter: zwol | Owner: atagar
Type: defect | Status: new
Priority: normal | Milestone: Tor: 0.2.5.x-final
Component: Stem | Version: Tor: 0.2.4.17-rc
Resolution: | Keywords: tor-relay
Actual Points: | Parent ID:
Points: |
------------------------+--------------------------------
Comment (by zwol):
You can likely call '`tor_process.communicate()`' from a daemon thread to
avoid this.
That is approximately the workaround I put into my code. May I suggest
that as a first step here, the present need to do something like this
should be documented?
I've dug through python's subprocess module for over an hour so far
trying to find a method to ignore further stdout content without a special
puller thread but no luck so far.
So I recognize that this probably would require changes to Tor as well as
Stem, but the fact that Stem needs to parse log messages in the first
place seems like the ''real'' bug here. What exactly is it doing with
them, and can we think of a better technique? Maybe a new command line
option which tells Tor to close file descriptor N when it reaches a
certain level of initializedness, or something like that?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9862#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list