Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #7591

Closed (moved)
(moved)
Open
Created Nov 29, 2012 by Trac@tracbot

"Bug: Duplicate call to connection_mark_for_close at directory.c"

After reading about bufferevents in the v0.2.3.25 release notes I added "--enable-bufferevents" to my Tor config. Now I intermittently get this error:

[warn] Bug: Duplicate call to connection_mark_for_close at directory.c:3571 (first at directory.c:3571)

By "intermittently" I mean I've gotten this error 19 times in the past 11 hours, logged in groups of 2 - 6 at a time.

No errors of this type are seen with v0.2.3.25 when not configuring for bufferevents.

Are bufferevents supposed to be ready for prime time, or is this still a feature in development?

Trac:
Username: tmpname0901

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