[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #7591 [Tor]: "Bug: Duplicate call to connection_mark_for_close at directory.c"

#7591: "Bug: Duplicate call to connection_mark_for_close at directory.c"
-------------------------+--------------------------------------------------
 Reporter:  tmpname0901  |          Owner:                    
     Type:  defect       |         Status:  new               
 Priority:  normal       |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor          |        Version:  Tor: 0.2.3.25     
 Keywords:               |         Parent:                    
   Points:               |   Actualpoints:                    
-------------------------+--------------------------------------------------
 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?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7591>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs