Thanks for the quick response.
Point taken. I cannot remember exactly when I first noticed the problem, but I do run nightly builds and update them every couple of days. I first noticed it some time ago. One torrent had been unintentionally left running since last Summer, and out of curiosity, I took note of the Time Elapsed data. Such a glaring discrepancy could hardly be missed!
The problem is genuine. Here are three updated grabs of the same fields, taken a few minutes before typing this response:
- Torrent 1 - Friday 25th February, about 01:45 UTC
- 4.jpg (14.97 KiB) Viewed 3816 times
- Torrent 2 - 25th Feb 2011
- 5.jpg (17.02 KiB) Viewed 3816 times
- Torrent 3 - also 25th February, 2011
- 6.jpg (19.49 KiB) Viewed 3816 times
Notice that the recorded elapsed times are shorter than in the previous shots.
I currently have 10 torrents running, and most of them are showing the same oddity. Two have only been started today. Another one has only been running for a week. This one is also recording incorrect times. Here is the full window:
- Newer Torrent
- Recent torrent.jpg (64.64 KiB) Viewed 3816 times
[Don't worry; this file was downloaded with the written permission of the owner. It is primarily disseminated via bit torrents.]
Notice that the downloading time is almost recorded properly, but that the displayed Seeding time is already wrong by about 6 days.
I've not been able to see exactly what is going on, but it strikes me that the clocks may be hitting some sort of threshold and then returning to a lower figure. All clocks are counting upwards in seconds and minutes, and nothing looks wrong until you work out the dates, and check with the displayed times.