[tor-bugs] #18994 [Applications/Tor Browser]: Tor crashes after tor browser update running bridge mode in Windows
Tor Bug Tracker & Wiki
blackhole at torproject.org
Mon May 9 02:47:34 UTC 2016
#18994: Tor crashes after tor browser update running bridge mode in Windows
--------------------------------------+------------------------------
Reporter: eli | Owner: tbb-team
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Applications/Tor Browser | Version: Tor: 0.2.7.6
Severity: Major | Resolution:
Keywords: tor broser, bridge mode | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------+------------------------------
Comment (by eli):
Replying to [comment:1 teor]:
> Please supply the warning log message that tor logs right before
exiting.
> It will tell us what's wrong with your torrc or Tor Browser, and help us
assign this
> bug ti the right component.
Here are the last lines from the last run that I closed down deliberately:
May 08 21:20:37.000 [notice] Bootstrapped 100%: Done
May 08 21:20:37.000 [notice] Now checking whether ORPort 71.126.229.56:443
is
reachable... (this may take up to 20 minutes -- look for log messages
indicating success)
May 08 21:20:38.000 [warn] Failure from drain_fd: No error
May 08 21:20:38.000 [notice] Self-testing indicates your ORPort is
reachable
from the outside. Excellent. Publishing server descriptor.
May 08 21:20:40.000 [notice] New control connection opened from 127.0.0.1.
May 08 21:20:40.000 [notice] New control connection opened from 127.0.0.1.
May 08 21:20:41.000 [notice] Performing bandwidth self-test...done.
May 08 21:27:27.000 [notice] Owning controller connection has closed --
exiting now.
May 08 21:27:27.000 [notice] Catching signal TERM, exiting cleanly.
Over many runs there has been no [warn] associated with the shutdown. The
warning "Failure from drain_fd: No error" shown seven lines above the
shutdown appears that close only because I shut down after it happened to
appear - in longer runs it occurs way before the shutdown.
The notice "Owning controller connection has closed -- exiting now" has
some
variations in other logs:
May 08 16:22:47.000 [notice] Monitored process 4128 is dead.
May 08 16:22:47.000 [notice] Owning controller process has vanished --
exiting now.
I hoped to catch the PID (I presume of firefox.exe or tor.exe) in this
last
run, but I got the variant shown first above.
The last notice "Catching signal TERM, exiting cleanly" always appears.
HTH, eliaz
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18994#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list