Even though I missed the IRC meeting today (sorry), I wanted to share that there has been a noticeable increase lately in support requests regarding a "Tor unexpectedly exited. Please restart the application." message.
Users will get this message over and over when trying to start their Tor Browser. At least some of these folks are already familiar with Tor Browser ("It worked fine before"). As a response, we will usually tell users to delete their current Tor Browser and download the Tor Browser again, which seems to usually clear up the issue. I have not opened a new ticket for this issue.
Matt Pagan:
Even though I missed the IRC meeting today (sorry), I wanted to share that there has been a noticeable increase lately in support requests regarding a "Tor unexpectedly exited. Please restart the application." message.
Users will get this message over and over when trying to start their Tor Browser. At least some of these folks are already familiar with Tor Browser ("It worked fine before"). As a response, we will usually tell users to delete their current Tor Browser and download the Tor Browser again, which seems to usually clear up the issue. I have not opened a new ticket for this issue.
This most frequently happens if something else (perhaps an abandoned tor process) is using one of Tor's network ports.
Out of curiosiry, do we know if these are PT/bridge users? 3.6-beta-1 users in general? Or all TBB users? Has it been observed on all platforms, or just one of them?
Mike Perry:
Matt Pagan:
Even though I missed the IRC meeting today (sorry), I wanted to share that there has been a noticeable increase lately in support requests regarding a "Tor unexpectedly exited. Please restart the application." message.
Users will get this message over and over when trying to start their Tor Browser. At least some of these folks are already familiar with Tor Browser ("It worked fine before"). As a response, we will usually tell users to delete their current Tor Browser and download the Tor Browser again, which seems to usually clear up the issue. I have not opened a new ticket for this issue.
This most frequently happens if something else (perhaps an abandoned tor process) is using one of Tor's network ports.
The error does not always happen after a new download, either. One user said his Tor Browser worked the night he downloaded it, and the next morning he got this message when he tried to start the browser again.
Out of curiosiry, do we know if these are PT/bridge users? 3.6-beta-1 users in general? Or all TBB users?
It's been observed in 3.5.3, sans pluggable transports.
Has it been observed on all platforms, or just one
of them?
I've seen this on Mac OS and Windows.
tbb-dev mailing list tbb-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tbb-dev
-
Matt Pagan -
Mike Perry