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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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
  • #26360

Closed (moved)
Open
Opened Jun 12, 2018 by David Fifield@dcf

Transport plugins deadlock if they write too much to stderr

launch_managed_proxy, via tor_spawn_background, opens a pipe from the child process's stderr, but never reads from the pipe. If the child process writes too much to its stderr, eventually an OS buffer fills up and the child process hangs. This manifests in the tor log as "No running bridges."

Seems like this has always been a problem, but it only showed up recently with Snowflake, which by default logs to stderr and is more chatty than past transports have been. See #25600 (moved). The problem went away when instructing snowflake-client to log to a file instead of to stderr.

Ccing ahf as suggested by arma.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#26360