Opened 13 years ago

Last modified 7 years ago

#307 closed defect (Fixed)

Win XP tor crash

Reported by: Moriarty Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: Moriarty Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Using Windows XP Pro, SP2.
Tor: 0.1.1.21 (which isn't in the "reported version" drop down box on this bug reporter!)

It seems Tor is unhappy. First it crashed. Now it seems to have made vidalia unstable (because I can't right-click it's taskbar icon), and when I try to run a new version of videlia I instantly get a:

"Vidalia detected Tor exiting unexpectedly"
This is the log from the start-up:

Jun 23 11:11:07:281 [Debug] conn_read_callback(): socket 1588 wants to read.
Jun 23 11:11:07:281 [Debug] conn_read_callback(): socket 1588 wants to read.
Jun 23 11:11:07:359 [Notice] Tor v0.1.1.21. This is experimental software. Do not rely on it for strong anonymity.
Jun 23 11:11:07:359 [Notice] Initialized libevent version 1.1a+imweasel using method win32. Good.
Jun 23 11:11:07:359 [Notice] connection_create_listener(): Opening Socks listener on 127.0.0.1:9050
Jun 23 11:11:07:359 [Warning] connection_create_listener(): Could not bind to 127.0.0.1:9050: Address already in use [WSAEADDRINUSE ]. Is Tor already running?
Jun 23 11:11:07:359 [Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
Jun 23 11:11:07:359 [Error] tor_init(): Reading config failed--see warnings above. For usage, try -h.

This bug is probably because there's another version of vidalia/tor running that I can't shut down without killing using task-manager. Either way if you try to run a second version at the same time as the first it should die more gracefully.

You'd probably get more bug reports if you didn't force people create an account.

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

Child Tickets

Change History (6)

comment:1 Changed 13 years ago by thalunil

I cannot reproduce your bug.
Have you installed 2 different versions?

comment:2 Changed 13 years ago by Moriarty

At the time I was running Tor I only had one copy of Tor installed.
Outside of this particular crash Tor did crash rather often (once to twice a day).
The tasks I was running would be:

Trillain (going through Tor).
Opera 9 (going through Tor)

Emule (_not_ going through Tor)

sygate personal firewall
daemon tool 4.03

So maybe one of them helped with the crashing.

comment:3 Changed 13 years ago by arma

This is a bug with Vidalia and its package, not with Tor.

Also, do all of your Tor "crashes" look like the above? This is correct behavior for Tor.

But I agree that a future Vidalia package should behave better -- stay tuned for Vidalia
0.0.6.

comment:4 Changed 13 years ago by edmanm

Vidalia 0.0.8 detects an existing instance of Tor and talks to that one, instead of starting another like you saw above. You can
test this out now if you want to run the latest svn version of Vidalia. See http://trac.vidalia-project.net/wiki/GettingTheCode for more information.

Regarding Vidalia becoming "unstable" when Tor crashes, let us know if you can tell us how to reproduce this and feel free to file
a report on our bug tracker at: http://trac.vidalia-project.net/newticket

comment:5 Changed 13 years ago by edmanm

flyspray2trac: bug closed.

comment:6 Changed 7 years ago by nickm

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