Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #43

Closed (moved)
Open
Created Dec 25, 2004 by Nick Mathewson@nickm🤹

Worker threads die vigorously on win32.

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]

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None