[tor-bugs] #27808 [Core Tor/Tor]: tor 0.3.5.early-alpha: Raw assertion failed at smartlist_core.c::191191 : idx>=0

[Tor Bug Tracker & Wiki]

#27808: tor 0.3.5.early-alpha: Raw assertion failed at smartlist_core.c::191191 :
idx>=0
---------------------------------+------------------------------------
 Reporter:  jchevali             |          Owner:  rl1987
     Type:  defect               |         Status:  needs_information
 Priority:  Very High            |      Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor         |        Version:  Tor: 0.3.5.1-alpha
 Severity:  Normal               |     Resolution:
 Keywords:  regression 035-must  |  Actual Points:
Parent ID:                       |         Points:
 Reviewer:                       |        Sponsor:
---------------------------------+------------------------------------

Comment (by jchevali):

 I've set the log level to info and I'm comparing a successful run with a
 failed run.

 For both runs, there's two entries logged by routerlist_remove_old_routers
 thirteen seconds after launch.  The two entries are separated by a pageful
 of other entries, but they seem to have the same log time (as do those
 other entries); or at least they appear to have the same time up to the
 second since there's no millisecond resolution (there is but it's 000).

 One minute after that, there's a further entry of
 routerlist_remove_old_routers in either log.  The successful run continues
 logging that every minute seemingly, while also doing other stuff.  The
 bad run crashes right after this last entry, with the following message:

 {{{
 INTERNAL ERROR: Raw assertion failed at
  src/lib/smartlist_core/smartlist_core.c:191: idx>=0
 ./tor(dump_stack_symbols_to_error_fds+0x31)[0x561de403a571]
 ./tor(tor_raw_assertion_failed_msg_+0x86)[0x561de403abf6]
 ./tor(smartlist_del+0xbf)[0x561de403936f]
 ./tor(retry_all_listeners+0x459)[0x561de3fc6939]
 ./tor(+0x533db)[0x561de3e9d3db]
 ./tor(+0x5bed1)[0x561de3ea5ed1]
 /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x22c05)[0x7f4acb72ac05]
 /usr/lib/x86_64-linux-
 gnu/libevent-2.1.so.6(event_base_loop+0x5a7)[0x7f4acb72b537]
 ./tor(do_main_loop+0x203)[0x561de3ea2843]
 ./tor(tor_run_main+0x11f5)[0x561de3ea4cc5]
 ./tor(tor_main+0x3a)[0x561de3e9d07a]
 ./tor(main+0x19)[0x561de3e9cbd9]
 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f4aca66eb45]
 ./tor(+0x52c29)[0x561de3e9cc29]
 }}}

 Here's the gist of my torrc besides the two entries discussed:
 {{{
 SOCKSPort 9050

 Log info file /var/log/tor/log

 RunAsDaemon 1

 ControlPort 9051
 HashedControlPassword ...

 HiddenServiceDir ...
 HiddenServiceVersion 3
 HiddenServicePort ...

 HiddenServiceDir ...
 HiddenServiceAuthorizeClient ...
 HiddenServiceVersion 2
 HiddenServicePort ...

 ORPort 9999
 ORPort [1234:5678::1]:9999

 Nickname ...

 RelayBandwidthRate ...
 RelayBandwidthBurst ...

 AccountingMax ...
 AccountingStart ...

 ContactInfo ...

 ExitPolicy reject *:*

 ExitRelay 0

 BridgeRelay 1

 MaxMemInQueues 256 MB
 AvoidDiskWrites 1
 PidFile /var/lib/tor/pid

 ServerTransportPlugin ...

 ExtORPort auto
 DisableDebuggerAttachment 0
 LongLivedPorts ...
 GeoIPFile /usr/share/tor/geoip
 GeoIPv6File /usr/share/tor/geoip6
 ExcludeNodes ...
 MaxConsensusAgeForDiffs 6 hours
 }}}

 I'm not using docker, though I could set one up with a little effort.

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