Opened 15 years ago

Last modified 7 years ago

#43 closed defect (Fixed)

Worker threads die vigorously on win32.

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

Description

When people try to run a Tor server on windows, it seems that their CPU worker threads and DNS threads too die badly. Or maybe the tor_socketpair stuff isn't really working.

[...]

Dec 25 07:55:03.156 [warn] connection_dns_reached_eof(): Read eof. Worker died unexpectedly.
Dec 25 07:55:03.156 [warn] connection_cpu_reached_eof(): Read eof. Worker died unexpectedly.

[...]

Also, these dead workers don't prevent Tor from reporting itself as working when the first circuit is built. That's probably bad.

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

Child Tickets

Change History (3)

comment:1 Changed 15 years ago by nickm

Oh, duh. We were calling tor_close_socket overzealously. I'll fix that and see if there are any other bugs at work.

comment:2 Changed 15 years ago by nickm

flyspray2trac: bug closed.
Fixed in CVS. We need to remember that we multithread on windows.

comment:3 Changed 7 years ago by nickm

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