Tor crashes on Windows when no bridges available
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:
two randomly selected "wrong" IPs, meaning there is no running bridge with that IP
Bridge 184.108.40.206:80 Bridge 220.127.116.11: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:
- Start Tor with some valid bridges and wait until bootstrapping is done.
- Stop Tor
- Go to DATADIR and remove all cached-* files
- Enter some wrong information about bridges (I just select some random IP addresses) and save the file
- 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]