Opened 10 years ago

Closed 9 years ago

Last modified 7 years ago

#1218 closed defect (worksforme)

Tor crashes on Windows when no bridges available

Reported by: kubieziel Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.2.1.21
Severity: Keywords:
Cc: kubieziel, nickm, Sebastian, karsten, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I'm running the Tor Browser bundle (Vidalia 0.2.6, Tor 0.2.1.21) on Windows XP and wanted to know
what happens, when information about bridges are wrong. Therefore I stopped Tor, deleted all consensus, descriptor
and geoip-files and edited the torrc:

AvoidDiskWrites 1
# two randomly selected "wrong" IPs, meaning there is no running bridge with that IP
Bridge 91.231.45.12:80
Bridge 141.35.112.65:443
ControlPort 9051
CookieAuthentication 1
DataDirectory .\Data\Tor
GeoIPFile .\Data\Tor\geoip
Log notice stdout
SocksListenAddress 127.0.0.1
UpdateBridgesFromAuthority 1
UseBridges 1

When I restarted Tor, it crashed and wanted to system crash reports. I'm not able to copy this report. But
it looks a bit like a core dump to me. If you have an idea how to copy this report or where it is saved, I can
send it.

The log file itself only has an info level entry:
Jan 18 12:09:47.546 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
You can download the debug-log at <URL:http://kubieziel.de/tmp/tor-log.zip>.

Steps to reproduce:

  1. Start Tor with some valid bridges and wait until bootstrapping is done.
  2. Stop Tor
  3. Go to DATADIR and remove all cached-* files
  4. Enter some wrong information about bridges (I just select some random IP addresses) and save the file
  5. Restart Tor

It only works if bridges are involved and if you first start Tor with "good" information. If the information
is "bad" from the first start of Tor, it just waits for the bridge (no crash).
At the moment I only tested this on Windows.

If there is any information missing please ask. I subscribed to this bug.

[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]

Child Tickets

Change History (6)

comment:1 Changed 10 years ago by kubieziel

Tested it with Tor 0.2.2.1-alpha (standard package from deb.tp.o) and can't reproduce it here.

comment:2 Changed 10 years ago by arma

Starting first with good bridges means your bridget info gets written
into the state file as entry guards.

I'm not sure how that would influence things though.

Btw, Tor 0.2.2.1-alpha is very old.

comment:3 Changed 10 years ago by kubieziel

Uups, this was a typo:
/usr/sbin/tor --version
Jan 18 22:02:33.789 [notice] Tor v0.2.2.6-alpha (git-0da554dbc594f573).

comment:4 Changed 10 years ago by kubieziel

I made several tries to reproduce this crash on other versions of Tor. But I can't neither reproduce it on the computer where it originally happened nor on any other computer (tried several versions of Tor). At the moment I have no idea how to make the crash reappear. So I would suggest closing this item. If I'll find out anything more about it, I'll report it again. Sorry for the noise.

comment:5 Changed 9 years ago by nickm

Resolution: Noneworksforme
Status: newclosed

Closing as worksforme; please let us know if this comes back

comment:6 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.