#32868: crash: Assertion node->rs->is_possible_guard failed in compute_weighted_bandwidths at ------------------------------+------------------------------------ Reporter: toralf | Owner: nickm Type: defect | Status: accepted Priority: High | Milestone: Tor: 0.4.2.x-final Component: Core Tor/Tor | Version: Tor: 0.4.2.5 Severity: Normal | Resolution: Keywords: regression crash | Actual Points: 0.6 Parent ID: | Points: 1 Reviewer: | Sponsor: ------------------------------+------------------------------------ Changes (by nickm):
* status: new => accepted * owner: (none) => nickm * actualpoints: 0.5 => 0.6 Comment: Okay, I'm pretty well stymied. I'm not sure where this RS is coming from, or how it's getting in this state. I think my best bet for now is to write a diagnostic patch to disable the assertion here, and instead log what we can find out about the routerstatus. Branch is: diagnose_32868_035 0.3.5 PR: https://github.com/torproject/tor/pull/1661 master PR: (for CI) https://github.com/torproject/tor/pull/1662 This won't fix the underlying problem, but I think we should consider merging it to help track the problem down. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32868#comment:8> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs