[tor-bugs] #9754 [Tor]: Tor 0.2.4.17-rc crashed with failed assertion

[Tor Bug Tracker & Wiki]

#9754: Tor 0.2.4.17-rc crashed with failed assertion
------------------------------+--------------------------------
     Reporter:  communicator  |      Owner:
         Type:  defect        |     Status:  needs_information
     Priority:  major         |  Milestone:  Tor: 0.2.4.x-final
    Component:  Tor           |    Version:  Tor: unspecified
   Resolution:                |   Keywords:  tor-relay
Actual Points:                |  Parent ID:
       Points:                |
------------------------------+--------------------------------

Comment (by communicator):

 Well, it took almost five days this time. The good news is: now I have a
 core file. The bad news: Tor crashed without the failed assertion from
 last time.

 Backtrace from gdb:

 {{{
 Core was generated by `/usr/bin/tor --defaults-torrc /usr/share/tor/tor-
 service-defaults-torrc --hush'.
 Program terminated with signal 6, Aborted.
 #0  0x00007f822b8ab1e5 in raise () from /lib/x86_64-linux-gnu/libc.so.6
 (gdb) bt
 #0  0x00007f822b8ab1e5 in raise () from /lib/x86_64-linux-gnu/libc.so.6
 #1  0x00007f822b8ae398 in abort () from /lib/x86_64-linux-gnu/libc.so.6
 #2  0x00007f822b8e67cb in ?? () from /lib/x86_64-linux-gnu/libc.so.6
 #3  0x00007f822b8f0a26 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
 #4  0x00007f822b8f17a3 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
 #5  0x00007f822d0b003f in circuitmux_detach_circuit (cmux=0x7f8235060760,
 circ=0x7f823354d160) at ../src/or/circuitmux.c:1061
 #6  0x00007f822d0a84db in circuit_set_circid_chan_helper
 (circ=circ at entry=0x7f823354d160, direction=direction at entry=1,
     id=id at entry=0, chan=chan at entry=0x0) at ../src/or/circuitlist.c:142
 #7  0x00007f822d0a8ab3 in circuit_set_p_circid_chan
 (circ=circ at entry=0x7f823354d160, id=id at entry=0, chan=chan at entry=0x0)
     at ../src/or/circuitlist.c:217
 #8  0x00007f822d0bc893 in command_process_destroy_cell (chan=<optimized
 out>, cell=<optimized out>) at ../src/or/command.c:506
 #9  command_process_cell (chan=<optimized out>, cell=0x7fff497c5870) at
 ../src/or/command.c:153
 #10 0x00007f822d09da1b in channel_tls_handle_cell
 (cell=cell at entry=0x7fff497c5870, conn=conn at entry=0x7f82341fccb0)
     at ../src/or/channeltls.c:923
 #11 0x00007f822d0ddc57 in connection_or_process_cells_from_inbuf
 (conn=0x7f82341fccb0) at ../src/or/connection_or.c:1972
 #12 0x00007f822d0e0ef2 in connection_or_process_inbuf
 (conn=conn at entry=0x7f82341fccb0) at ../src/or/connection_or.c:483
 #13 0x00007f822d0cc4c5 in connection_process_inbuf
 (conn=conn at entry=0x7f82341fccb0, package_partial=package_partial at entry=1)
     at ../src/or/connection.c:4001
 #14 0x00007f822d0d265d in connection_handle_read_impl
 (conn=0x7f82341fccb0) at ../src/or/connection.c:2839
 #15 connection_handle_read (conn=conn at entry=0x7f82341fccb0) at
 ../src/or/connection.c:2880
 #16 0x00007f822d02e061 in conn_read_callback (fd=<optimized out>,
 event=<optimized out>, _conn=0x7f82341fccb0)
     at ../src/or/main.c:718
 #17 0x00007f822c6a8ccc in event_base_loop () from /usr/lib/x86_64-linux-
 gnu/libevent-2.0.so.5
 #18 0x00007f822d02e9f5 in do_main_loop () at ../src/or/main.c:1992
 #19 0x00007f822d0301de in tor_main (argc=4, argv=0x7fff497c5fb8) at
 ../src/or/main.c:2708
 #20 0x00007f822b897995 in __libc_start_main () from /lib/x86_64-linux-
 gnu/libc.so.6
 #21 0x00007f822d02aabb in _start ()
 }}}

 Is this a different story?
 Do you need further information (which gdb commands)?

 Next crash coming in 3-5 days. ;-)

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