Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Browser Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 831
    • Issues 831
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor BrowserTor Browser
  • Issues
  • #41549
Closed
Open
Issue created Dec 31, 2022 by trinity-1686a@trinity-1686a🤖

tor freeze when receiving to many http proxy requests on socks port

After receiving 724 curl 127.0.0.1:9150 (number was very consistent for me, but maybe somehow platform dependent?), tor stop doing anything. I can't reproduce that issue with a tor not started by TB. Arma intuition is it could be TB isn't reading tor logs "fast enough" so tor end up blocked on trying to write to its stdout.

Note: these requests are invalid by tor standards: tor does not accept http requests on its socks port, and answer them with a basic "this is not how to use tor" webpage (and logs a complain).

Edit: setting Log warn stdout causes the error to appear after 740 curls, and Log err stdout make it never is an issue, so it is indeed an issue of not reading tor stdout fast enough (or at all possibly?), and getting blocked when the pipe is full.

Edited Dec 31, 2022 by trinity-1686a
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking