Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#44332 - [tor] 0.2.5.10-1 tor_assertion_failed_(): Bug: src/or/buffers.c:2627 (Fixed upstream)

Attached to Project: Arch Linux
Opened by Sarah Harvey (worldwise001) - Wednesday, 25 March 2015, 06:00 GMT
Last edited by Lukas Fleischer (lfleischer) - Friday, 10 April 2015, 10:13 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Tor release 0.2.5.10-1 has an assert fail, crashing the program with this stack trace:
Mar 23 07:18:26.000 [err] Bug: Assertion ch->data < &ch->mem[0]+ch->memlen failed in assert_buf_ok at src/or/buffers.c:2627. Stack trace:
Mar 23 07:18:26.000 [err] Bug: /usr/bin/tor(log_backtrace+0x41) [0x7f93f7c487c1]
Mar 23 07:18:26.000 [err] Bug: /usr/bin/tor(tor_assertion_failed_+0x8c) [0x7f93f7c5494c]
Mar 23 07:18:26.000 [err] Bug: /usr/bin/tor(assert_buf_ok+0x137) [0x7f93f7bc2737]
Mar 23 07:18:26.000 [err] Bug: /usr/bin/tor(assert_connection_ok+0xdc) [0x7f93f7bfdb3c]
Mar 23 07:18:26.000 [err] Bug: /usr/bin/tor(+0x30f87) [0x7f93f7b69f87]
Mar 23 07:18:26.000 [err] Bug: /usr/lib/libevent-2.0.so.5(event_base_loop+0x806) [0x7f93f71c1ca6]
Mar 23 07:18:26.000 [err] Bug: /usr/bin/tor(do_main_loop+0x194) [0x7f93f7b6b754]
Mar 23 07:18:26.000 [err] Bug: /usr/bin/tor(tor_main+0x1705) [0x7f93f7b6e585]
Mar 23 07:18:26.000 [err] Bug: /usr/lib/libc.so.6(__libc_start_main+0xf0) [0x7f93f651a800]
Mar 23 07:18:26.000 [err] Bug: /usr/bin/tor(+0x2ecfb) [0x7f93f7b67cfb]

This is apparently already fixed upstream: https://trac.torproject.org/projects/tor/ticket/15083 . Thus a new package just needs to be rolled out, probably as 0.2.5.10-2.

Steps to reproduce:
Configure a default tor relay
Run: systemctl start tor
Wait some time until crash.

Other notes:
If this appears to be hard to reproduce, I can test possible candidate packages since I run a high-traffic tor relay, so the probability of it crashing will probably be significantly higher on my end.

This graph also shows the apparent downtime (the delay is because I rely on torweather to send me a notice when tor goes down):
https://atlas.torproject.org/#details/39F096961ED2576975C866D450373A9913AFDC92
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Friday, 10 April 2015, 10:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 0.2.5.11-1.
Comment by Doug Newgard (Scimmia) - Wednesday, 25 March 2015, 15:50 GMT
Looking at the dates on the bug tracker, I'm guessing the fix is in 0.2.5.11?
Comment by Sarah Harvey (worldwise001) - Wednesday, 25 March 2015, 16:50 GMT
I just looked at the tor release, and it appears you are probably correct. Sorry I didn't read carefully, and it was coincidental that 0.2.5.11 was released just yesterday.

Changelog:
https://blog.torproject.org/blog/tor-02426-and-02511-are-released

Loading...