[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #23696 [Core Tor/Tor]: Bug: scheduler_kist.c:520: kist_scheduler_schedule: Non-fatal assertion !((diff < 0)) failed.
#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, tor-sched, 0.3.2.2 | Actual Points:
-alpha-must |
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Changes (by cypherpunks):
* status: needs_information => new
* keywords: tor-client, tor-sched, easy, 0.3.2.2-alpha-must => tor-client,
tor-sched, 0.3.2.2-alpha-must
Comment:
Replying to [comment:14 dgoulet]:
> Replying to [comment:13 cypherpunks]:
> > After hibernation on Windows 7:
>
> But before that, it was running properly right?
Visually - yes, but who knows ;)
> So it basically was running then hibernation and then came back and
boom?
No boom, just logs :)
> Do you recall the length of time that it was in hibernation?
No. Is it meaningful?
> Was it in the range of minutes or days?
Hours.
Here is a new sample:
{{{
Tor NOTICE: Your system clock just jumped 47582 seconds forward; assuming
established circuits no longer work.
Tor NOTICE: Heartbeat: Tor's uptime is 1 day 4:22 hours, with 0 circuits
open. I've sent 10.84 MB and received 82.03 MB.
Tor NOTICE: Average packaged cell fullness: 57.419%. TLS write overhead:
4%
[12-04 07:00:02] Torbutton INFO: tor catchall circuit has been dirty for
over 10 minutes. Rotating.
[12-04 07:00:02] Torbutton INFO: New domain isolation for --unknown--:
c17295dbb878f7b7cdeacddaa85791f2
[12-04 07:00:02] Torbutton INFO: tor SOCKS:
https://aus1.torproject.org/torbrowser/update_3/alpha/WINNT_x86-gcc3-x86/7.5a8
/en-US via
--unknown--:c17295dbb878f7b7cdeacddaa85791f2
Tor WARN: Failed to find node for hop #1 of our path. Discarding this
circuit.
[12-04 07:02:03] Torbutton INFO: controlPort >> 650 STREAM 2081 FAILED 0
aus1.torproject.org:443 REASON=TIMEOUT
[12-04 07:02:03] Torbutton INFO: controlPort >> 650 STREAM 2081 CLOSED 0
aus1.torproject.org:443 REASON=TIMEOUT
Tor NOTICE: Tried for 120 seconds to get a connection to [scrubbed]:443.
Giving up. (waiting for circuit)
Tor WARN: tor_bug_occurred_(): Bug: scheduler_kist.c:530:
kist_scheduler_schedule: Non-fatal assertion !((diff < 0)) failed. (Future
instances of this warning will be silenced.) (on Tor 0.3.2.4-alpha )
Tor WARN: Bug: Non-fatal assertion !((diff < 0)) failed in
kist_scheduler_schedule at scheduler_kist.c:530. (Stack trace not
available) (on Tor 0.3.2.4-alpha )
Tor NOTICE: Tor has successfully opened a circuit. Looks like client
functionality is working.
}}}
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23696#comment:15>
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