[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):

 Replying to [comment:53 nickm]:
 > New instance with 0.2.5.8-rc reported in #13481:

 #13481 is probably related and not fully duplicate of this bug.
 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.
 nodelist_set_consensus() called only for usable_consensus_flavor()
 (FLAV_MICRODESC for client and FLAV_NS for relay). While client mode
 enabled nodelist_set_consensus() changes node->md, and skips it if relay
 mode enabled, then if node->rs exist for given ns consensus then such node
 can't be purged.
 Probably valid explanation, if nothing missed.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7164#comment:56>
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