[tor-bugs] #23696 [Core Tor/Tor]: Bug: scheduler_kist.c:520: kist_scheduler_schedule: Non-fatal assertion !((diff < 0)) failed.

[Tor Bug Tracker & Wiki]

#23696: Bug: scheduler_kist.c:520: kist_scheduler_schedule: Non-fatal assertion
!((diff < 0)) failed.
--------------------------+------------------------------------
 Reporter:  cypherpunks   |          Owner:  (none)
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |        Version:  Tor: 0.3.2.1-alpha
 Severity:  Normal        |     Resolution:
 Keywords:  tor-client    |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------

Comment (by pastly):

 Replying to [comment:2 arma]:
 > Question for pastly:
 >
 > A) This is on Windows -- is the kist scheduler supposed to be picked
 here? Is it supposed to be kistlite or something? (I still haven't read
 all the code.)
 >

 I'm guessing KISTLite was used from the beginning. They both use the same
 code, except for ~1 function (not this one).

 If Tor switched during runtime, it should have logged the switch and
 probably a reason why.

 Regardless, I'm betting this is a failure of monotime actually being
 monotonic. Or ... if this was literally right away on startup and if we
 can't assume statically-allocated memory on Windows is initialized to 0,
 then it's possible `scheduler_last_run` was garbage and larger than `now`.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23696#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online