[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #4697 [Tor Relay]: Assertion connection_state_is_connecting(conn) failed; aborting
#4697: Assertion connection_state_is_connecting(conn) failed; aborting
--------------------------+-------------------------------------------------
Reporter: keb | Owner:
Type: defect | Status: new
Priority: critical | Milestone: Tor: 0.2.3.x-final
Component: Tor Relay | Version: Tor: 0.2.3.9-alpha
Keywords: bufferevents | Parent:
Points: | Actualpoints:
--------------------------+-------------------------------------------------
Comment(by rransom):
I just saw that keb had attached new logs. (Trac doesn't send e-mail
notifications for new attachments.)
The important lines are right at the end:
{{{
Dec 13 03:07:09.000 [debug] connection_handle_event_cb(): event occurred
on conn 75 (Exit connecting (marked for close))
Dec 13 03:07:09.000 [err] connection_handle_event_cb(): Bug:
connection.c:2971: connection_handle_event_cb: Assertion
connection_state_is_connecting(conn) failed; aborting.
}}}
So an exit connection was marked for close before it had finished
connecting. Can we just ignore _CONNECTED events for connections that are
already marked for close? Can we ignore ''all'' events for connections
that are already marked for close?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4697#comment:13>
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