[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #23693 [Core Tor/Tor]: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-------------------------------------------------+-------------------------
Reporter: alif | Owner: nickm
Type: defect | Status:
| needs_revision
Priority: Medium | Milestone: Tor:
| 0.3.4.x-final
Component: Core Tor/Tor | Version: Tor:
| 0.3.1.9
Severity: Normal | Resolution:
Keywords: prop286, 034-triage-20180328, | Actual Points:
034-must crash 033-backport 032-backport |
031-backport |
Parent ID: | Points:
Reviewer: asn | Sponsor:
-------------------------------------------------+-------------------------
Comment (by teor):
Maybe we will deprecate DirPort some time in the future. Maybe we won't,
There are bootstrapping and diagnostic issues.
But here are some questions we can answer right now:
* Do we support DirPort without ORPort?
* If we do, when was the last Tor release that it actually worked?
* Why don't we have any tests for DirPort only operation?
As far as I can tell, people who get this bug seem to be setting DirPort
as a workaround.
They don't actually want to serve descriptors, they just want them
available locally.
If we can't find a use case that involves serving descriptors, I think we
should:
* fix the hibernation options so they allow people to download descriptors
every hour if that's what they need, then
* deprecate DirPort-only operation
But I'm not sure if we can remove features as a backport, so we are stuck
with fixing crashes like this (or saying "don't do that").
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23693#comment:34>
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