With Tor 0.4.8.17 running on ElectroBSD 14.3-STABLE I
reproducible get assertion failures at exit:
####
Jul 28 13:25:32.633 [notice] Tor 0.4.8.17 (git-e41649c9a34f39f1) running on
ElectroBSD with Libevent 2.1.12-stable, OpenSSL 3.0.16, Zlib 1.3.1, Liblzma
5.6.3, Libzstd 1.5.7 and BSD 1403502 as libc.
[...]
Jul 28 13:25:42.140 [notice] {GENERAL} Catching signal TERM, exiting cleanly.
Jul 28 13:25:42.141 [debug] {CIRC} pathbias_count_circs_in_states: Found opened
circuit 1 in path_state use succeeded
Jul 28 13:25:42.141 [debug] {CIRC} pathbias_count_circs_in_states: Found opened
circuit 1 in path_state use succeeded
Jul 28 13:25:42.141 [debug] {CIRC} pathbias_count_circs_in_states: Found opened
circuit 8 in path_state build succeeded
Jul 28 13:25:42.141 [debug] {CIRC} pathbias_count_circs_in_states: Found opened
circuit 9 in path_state build succeeded
Jul 28 13:25:42.143 [debug] {FS} tor_rename: Renaming /var/db/tor/state.tmp to
/var/db/tor/state
Jul 28 13:25:42.144 [info] {GENERAL} or_state_save: Saved state to
"/var/db/tor/state"
Jul 28 13:25:42.144 [debug] {GENERAL} threadpool_stop_threads: Signaled worker
threads to exit. Waiting for them to exit...
Jul 28 13:25:42.144 [debug] {GENERAL} worker_thread_main: Worker thread 1/4 has
exited [TID: 35948775929864].
============================================================ T=Jul 28
13:25:42.144 [debug] {GENERAL} worker_thread_main: Worker thread 2/4 has exited
[TID: 35948775927816].
Jul 28 13:25:42.144 [debug] {GENERAL} worker_thread_main: Worker thread 3/4 has
exited [TID: 35948775913480].
Jul 28 13:25:42.144 [debug] {GENERAL} worker_thread_main: Worker thread 4/4 has
exited [TID: 35948775931912].
============================================================ T= 1753701942
1753701942
INTERNAL ERROR: Raw assertion failed in Tor 0.4.8.17
(git-e41649c9a34f39f1)INTERNAL ERROR: Raw assertion failed in at Tor 0.4.8.17
(git-e41649c9a34f39f1) at
src/lib/lock/compat_mutex_pthreads.csrc/lib/lock/compat_mutex_pthreads.c::7891:
: 00
Error unlocking a mutex.
Error locking a mutex.
0x54eff23fd96 <dump_stack_symbols_to_error_fds+0x56> at /usr/local/bin/tor
0x54eff240ae8 <tor_raw_assertion_failed_msg_+0x1b8> at /usr/local/bin/tor
0x54eff24aab1 <tor_mutex_release+0x51> at /usr/local/bin/tor
0x54eff244815 <worker_thread_main+0x54efef43165> at /usr/local/bin/tor
0x54eff261d40 <tor_pthread_helper_fn+0x54efef43050> at /usr/local/bin/tor
0x54eff23fd96 <dump_stack_symbols_to_error_fds+0x56> at /usr/local/bin/tor
0x54eff240ae8 <tor_raw_assertion_failed_msg_+0x1b8> at /usr/local/bin/tor
0x54eff24aa31 <tor_mutex_acquire+0x51> at /usr/local/bin/tor
0x54eff244103 <threadpool_free_+0x93> at /usr/local/bin/tor
0x54eff15c900 <cpuworker_free_all+0x20> at /usr/local/bin/tor
0x54eff1e4f7e <tor_free_all+0x2e> at /usr/local/bin/tor
0x54eff081141 <tor_run_main+0x551> at /usr/local/bin/tor
0x54eff07f6c1 <tor_main+0x51> at /usr/local/bin/tor
0x54eff07f3a9 <main+0x19> at /usr/local/bin/tor
0x5572769ae64 <__libc_start1+0x124> at /lib/libc.so.7
Abort trap
####
It looks like the problem was introduced in ee9b3c127c180.
Reverting that commit works around the issue.
Fabian
_______________________________________________
tor-dev mailing list -- tor-dev@lists.torproject.org
To unsubscribe send an email to tor-dev-le...@lists.torproject.org
