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

Re: [tor-bugs] #7164 [Core Tor/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:  nickm
     Type:  defect                               |         Status:
                                                 |  needs_revision
 Priority:  High                                 |      Milestone:  Tor:
                                                 |  unspecified
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  0.2.4.19
 Severity:  Normal                               |     Resolution:
 Keywords:  tor-client, 025-backport, nickm-     |  Actual Points:
  should-review, review-group-24,                |
  033-triage-20180320, 033-removed-20180320      |
Parent ID:                                       |         Points:  2
 Reviewer:  asn                                  |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by cypherpunks):

 After syncing time in ticket:19460#comment:6 and hibernation, Tor shows
 {{{
 Tor NOTICE: Heartbeat: Tor's uptime is 13 days 0:41 hours, with 3 circuits
 open. I've sent 110.30 MB and received 728.68 MB.
 }}}
 but then
 {{{
 Tor WARN: microdesc_cache_clean(): Bug: Microdescriptor seemed very old
 (last listed 168 hours ago vs 168 hour cutoff), but is still marked as
 being held by 1 node(s). I found 1 node(s) holding it. Current
 networkstatus is 11 hours old. Hashtable badness is 0. (on Tor 0.3.2.10 )
 Tor WARN: microdesc_cache_clean(): Bug:   [0]:
 ID=0E71008524180D47796858A79EEC0F2233568B59. md=027FF798, rs=020E2B68,
 ri=00000000. Microdesc digest in RS matches. RS okay in networkstatus. (on
 Tor 0.3.2.10 )
 Tor NOTICE: Your system clock just jumped 38542 seconds forward; assuming
 established circuits no longer work.
 Tor NOTICE: Heartbeat: Tor's uptime is 13 days 3:58 hours, with 0 circuits
 open. I've sent 110.95 MB and received 732.77 MB.
 Tor NOTICE: Average packaged cell fullness: 61.425%. TLS write overhead:
 5%
 Tor NOTICE: Tor has successfully opened a circuit. Looks like client
 functionality is working.
 }}}
 So, Tor thinks 3:17 hours = 38542 seconds and also shows this bug.

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