[tor-bugs] #23693 [Core Tor/Tor]: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
--------------------------+------------------------------------
 Reporter:  alif          |          Owner:  nickm
     Type:  defect        |         Status:  reopened
 Priority:  Medium        |      Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |        Version:  Tor: 0.3.1.9
 Severity:  Normal        |     Resolution:
 Keywords:  prop286       |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------
Changes (by teor):

 * keywords:  029-backport, 030-backport, 031-backport, review-group-24 =>
     prop286
 * version:  Tor: 0.3.1.7 => Tor: 0.3.1.9


Comment:

 Replying to [comment:17 rustybird]:
 > > (please reopen if this bug occurs in any version released _after_
 today.)
 >
 > It still occurs if `server_mode()` is false but `dir_server_mode()` is
 true. Doesn't seem to make a difference (with 0.3.1.9) if it is set up
 like that in `torrc` on startup, or the result of being reconfigured.
 >
 > (Use case for this configuration: http://github.com/rustybird/corridor
 calls `SETCONF DirPort="127.0.0.1:9030 NoAdvertise"` to ensure the client
 continues to refresh the consensus even when dormant.)

 Running a directory mirror will cause a lot of unnecessary load and disk
 usage, particularly with newer tor versions. You'll generate a whole bunch
 of compressed diffs that you'll never serve.

 Try using `FetchDirInfoEarly 1` instead. If this doesn't work, just issue
 a RESOLVE request to a common address every hour or two at random, to keep
 tor alive. We have a proposal for a better controller API for this.

 Also, if you want a consensus with IPv6 addresses on a client, use
 `UseMicrodescriptors 0`.

 If you don't care about descriptors, and want to save bandwidth, use
 `FetchServerDescriptors 0`. You might find some bugs using this option,
 it's not well-tested.

 You can set `SOCKSPort 0` if you're not using it. It might add a bit of
 security.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23693#comment:20>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online