Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 318
    • Issues 318
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #8298
Closed
Open
Created Feb 21, 2013 by cypherpunks@cypherpunks

Do not start write to connection if blocked on bw

Tor can to start write to connection just because something wrote to conn's outbuf by _connection_write_to_buf_impl(). While connection can be blocked on bw still. If buckets empty it can't to write anything anyway (need investigation for sure).

Suggested idea to fix, could be looks like:

  if (conn->write_event && !conn->write_blocked_on_bw) {
    connection_start_writing(conn);
  }

Kludgy probably. legacy/trac#8111 (moved) will fix it generally for 0.2.5 I hopes.

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