12-03-2016, 11:49 AM
I recently noticed on the statistics page that my total uptime was only 93 days. As a decade+ user of Vuze, this confused me. I thought somehow the stats had reset, except that my total upload/download stats had clearly not reset. Only the uptime seemed to have been lost.
Unfortunately, 93 days was too long to simply pull the stats file from my 90 day incremental nightly backups. However, I was able to find a ~14 month old copy of my statistics file my my previous desktop. I pulled the uptime seconds from that file, added 14 months worth of seconds to try to get the value roughly back to where it should be, and put 322032610 (10.2 years) in my current statistics file and started up Vuze.
I went right to the stats page and it showed 10y77d. Success!
But wait! At exactly 1m1s of session uptime, the total uptime value changed from 10y77d to 1m1s and the two numbers now matched.
285291010 is a working value, while 322032610 wraps. Somewhere in-between those two values is the cutoff where Vuze wraps the counter. Both values are 29 bits long so it isn't an obvious bit length issue:
10001000000010011001000000010
10011001100011101001111100010
System details:
Java 1.8.0_51 (64 bit)
Oracle Corporation
c:\program files\vuze\jre
SWT v4508, win32
Windows 8.1 v6.3, amd64
V5.7.4.0/4 az3
And here's my full azureus.statistics file that will work for 1 minute before wrapping:
d3:alld12:d_downloadedi3491556660100e10:d_uploadedi2379751405465e8:dht_downi507379498456e6:dht_upi708976908731e10:downloadedi3894132620338e15:mark_downloadedi0e9:mark_timei0e13:mark_uploadedi0e11:mark_uptimei0e12:p_downloadedi59077410331e10:p_uploadedi79009739322e8:uploadedi5635896965392e6:uptimei322032610eee
Unfortunately, 93 days was too long to simply pull the stats file from my 90 day incremental nightly backups. However, I was able to find a ~14 month old copy of my statistics file my my previous desktop. I pulled the uptime seconds from that file, added 14 months worth of seconds to try to get the value roughly back to where it should be, and put 322032610 (10.2 years) in my current statistics file and started up Vuze.
I went right to the stats page and it showed 10y77d. Success!
But wait! At exactly 1m1s of session uptime, the total uptime value changed from 10y77d to 1m1s and the two numbers now matched.
285291010 is a working value, while 322032610 wraps. Somewhere in-between those two values is the cutoff where Vuze wraps the counter. Both values are 29 bits long so it isn't an obvious bit length issue:
10001000000010011001000000010
10011001100011101001111100010
System details:
Java 1.8.0_51 (64 bit)
Oracle Corporation
c:\program files\vuze\jre
SWT v4508, win32
Windows 8.1 v6.3, amd64
V5.7.4.0/4 az3
And here's my full azureus.statistics file that will work for 1 minute before wrapping:
d3:alld12:d_downloadedi3491556660100e10:d_uploadedi2379751405465e8:dht_downi507379498456e6:dht_upi708976908731e10:downloadedi3894132620338e15:mark_downloadedi0e9:mark_timei0e13:mark_uploadedi0e11:mark_uptimei0e12:p_downloadedi59077410331e10:p_uploadedi79009739322e8:uploadedi5635896965392e6:uptimei322032610eee