Page 1 of 1

Invalid uptime reported

PostPosted: 10 Jan 2016 06:34
by ale5000

Re: Invalid uptime reported

PostPosted: 10 Jan 2016 06:42
by raspopov
Looks like DWORD with time was wrapped. In many places Shareaza still using DWORD (32-bit) for time measuring and it's start shows wrong values after 49.7 day from Windows start (it can be on servers and never-rebooted notebooks).

Re: Invalid uptime reported

PostPosted: 10 Jan 2016 06:48
by ale5000
And about reporting repetitively the same GWC 15 times?
It shouldn't re-report the same GWC every time if the previous reporting is failed, it should be random every time.

Re: Invalid uptime reported

PostPosted: 10 Jan 2016 06:57
by raspopov
Exactly, with wrapped time Shareaza always think "I reported to this GWC too long ago, need update."

Re: Invalid uptime reported

PostPosted: 10 Jan 2016 07:02
by ale5000
But Shareaza shouldn't just report the one reported earliest in the past, but a random one from the list of reported earlier; this is safer in every case.

Re: Invalid uptime reported

PostPosted: 10 Jan 2016 07:04
by raspopov
It's just an assumption.