[tor-bugs] #7267 [Tor]: src/or/channel.c:1315 channel_closed: Assertion chan->state == CHANNEL_STATE_CLOSING || chan->state == CHANNEL_STATE_CLOSED || chan->state == CHANNEL_STATE_ERROR failed;

[Tor Bug Tracker & Wiki]

#7267: src/or/channel.c:1315 channel_closed: Assertion chan->state ==
CHANNEL_STATE_CLOSING || chan->state == CHANNEL_STATE_CLOSED || chan->state
== CHANNEL_STATE_ERROR failed;
-----------------------+----------------------------------------------------
 Reporter:  asn        |          Owner:                    
     Type:  defect     |         Status:  needs_review      
 Priority:  major      |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor        |        Version:  Tor: 0.2.4.4-alpha
 Keywords:  tor-relay  |         Parent:                    
   Points:             |   Actualpoints:                    
-----------------------+----------------------------------------------------

Comment(by mr-4):

 Replying to [comment:30 andrea]:
 > > My messages are exactly the same: "Something tried to close an
 or_connection_t without going through channels at
 src/or/connection.c:3120"
 > Yeah, that's possible.  Did you build with bufferevents enabled, by any
 chance?
 Indeed I have.

 If it is of any help, when idle (tor not used to relay traffic), I get
 this message appearing in my logs in a batch of about 10 every 60 minutes
 *exactly*, so it must be something tor is attempting to do, which relates
 to the "dead" bridges in my torrc file.

 If you include a bunch of "dead" bridges in your torrc file, you may be
 able to reproduce the problem (if you need a list of those, I'd gladly
 provide it - just let me know).

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7267#comment:33>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online