Changes between Initial Version and Version 1 of Ticket #20890, comment 13


Ignore:
Timestamp:
May 19, 2018, 12:33:28 PM (17 months ago)
Author:
TimeForGoToBed
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #20890, comment 13

    initial v1  
    1 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. 
     1Thanks, 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's 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. 
    22
    33While 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.