[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #20890 [Applications/Tor Launcher]: Increase connection timeout to avoid "Could not connect to Tor control port" errors



#20890: Increase connection timeout to avoid "Could not connect to Tor control
port" errors
-------------------------------------------------+------------------------
 Reporter:  torrc591                             |          Owner:  brade
     Type:  defect                               |         Status:  closed
 Priority:  Medium                               |      Milestone:
Component:  Applications/Tor Launcher            |        Version:
 Severity:  Normal                               |     Resolution:  fixed
 Keywords:  TorBrowserTeam201805R, tbb-backport  |  Actual Points:
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+------------------------

Comment (by TimeForGoToBed):

 Thanks, guys.  Glad you erred on the side of caution and made the new
 timeout a full 5 minutes.  As it turns out, I was premature in reporting
 that I was no longer experiencing the "Could not connect" issue.  While it
 was no longer the case, as in older versions of Tor Browser, that it would
 //never// succeed in connecting to the control port after the first post-
 install run, I've found that if my netbook is running other applications,
 the "Could not connect" returns.

 While experiencing the issue today, I tried various things that were
 unsuccessful in getting Tor Browser to successfully start up, including
 plugging into AC power to go to full-performance mode, switching from Wi-
 Fi to EtherNet, switching the priority of tor.exe and/or firefox.exe to
 High in the Task Manager just after startup, and even quitting all the
 other apps I was running.  Only rebooting got Tor to work again.  Intel,
 in their infinite wisdom, elected to limit my Atom CPU to being able to
 access 2 GB of RAM, so memory fragmentation and/or swapping may be
 responsible for the system being too slow to start up Tor within 30
 seconds unless a reboot is done.

 In any case, hope this does get backported to the next stable release;
 increasing the timeout seems like quite a safe change.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20890#comment:13>
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