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

 7 days to trigger bug:
 day 0: user launches Tor, fetches md (which later fails) and caches it
 with last_listed = 0 to disk;
 day 1: user online; restarting, shutdowning etc;
 day 2: user online, relay still announcing the same keys as for md from
 cache, no cached md changes;
 day 3: the same;
 day 4: the same;
 day 5: user offline;
 day 6: user offline;

 day 7: user starting Tor, cached consensus is several days old; md's
 last_listed stored on disk is zero; `update_microdescs_from_networkstatus`
 can't to update last_listed field in memory anymore; if
 `microdesc_cache_clean` launched before new consensus arrived and
 "last_listed < today - 7days" then bug triggeres.

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