[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #7164 [Tor]: microdesc.c:378: Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1

#7164: microdesc.c:378: Bug: microdesc_free() called, but md was still referenced
1 node(s); held_by_nodes == 1
------------------------+-------------------------------------------------
     Reporter:  jaj123  |      Owner:
         Type:  defect  |     Status:  needs_information
     Priority:  major   |  Milestone:  Tor: 0.2.???
    Component:  Tor     |    Version:  Tor: 0.2.4.19
   Resolution:          |   Keywords:  tor-client 024-backport 025-triaged
Actual Points:          |  Parent ID:
       Points:          |
------------------------+-------------------------------------------------

Comment (by cypherpunks):

 > Bunch of "md was still referenced" should be able to trigger if to
 launch tor as client and to change it to relay mode after all stuff
 fetched then wait for a week or so.

 Yet way to trigger bug is to use bridges, if one bridge supports md and
 another bridge have no md support. Client switches to ns-consensus after
 bridge that supports md fails circuit. Then client leaving pointers
 (node->md) and md unchanged, so bug depends cached stuff (@last-listed
 values) and client uptime. However, this scenario, if it was confirmed
 yet, shouldn't be actual today, md supported since 0.2.3.1-alpha version
 and 0.2.3.x is outdated.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7164#comment:59>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs