#24826: LZMA-compressed consensus diffs stall Tor Browser launch for at least 20s or break it entirely --------------------------+------------------------------------ Reporter: gk | Owner: (none) Type: defect | Status: new Priority: Medium | Milestone: Tor: 0.3.3.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: --------------------------+------------------------------------
Comment (by mcs): For reference: * The control port read timeout that is used by Tor Launcher is 15 seconds (used when reading Tor configuration via the control port, to issue commands during startup such as `TAKEOWNERSHIP`, and so on). * The control port read timeout that is used by Torbutton is 2 seconds (used when sending control port commands for the local SOCKS port check during browser startup and for new identity). Should these timeouts be increased? What value should we use? As someone pointed out, in an ideal world tor would be responsive to control port commands at all times. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24826#comment:7> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs