Opened 8 years ago

Closed 4 years ago

#7591 closed defect (wontfix)

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

Reported by: tmpname0901 Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor:
Severity: Keywords: tor-relay bufferevents
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


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?

Child Tickets

Change History (3)

comment:1 Changed 8 years ago by nickm

Keywords: tor-relay bufferevents added

Bufferevents were supposed to be ready for prime time, but it seems that they weren't. I'll look into this one, but I'd suggest not using bufferevents for now, unless you like finding new and exciting bugs.

comment:2 Changed 7 years ago by nickm

Milestone: Tor: 0.2.3.x-finalTor: unspecified

comment:3 Changed 4 years ago by nickm

Resolution: wontfix
Status: newclosed

The bufferevents code and corresponding build options have been removed in

Note: See TracTickets for help on using tickets.