Progress ("Done") and total Downloaded not syncing correctly[?] #123

Closed
opened 2026-02-21 14:53:16 -05:00 by deekerman · 9 comments
Owner

Originally created by @asamy on GitHub (Oct 3, 2012).

The % is not probably syncing after (let's say power outage or system reboot basically) & on a slow connection.

Screenshots:
progress
total

qBittorrent v3.0.2
Qt 4.8.2
Boost v1.5.0
Libtorrent v0.16.3.0
OS: ArchLinux 32bit

P.S: Force recheck gives same results too :| so I guess i'm screwed?
Let me know if more information is needed.

Originally created by @asamy on GitHub (Oct 3, 2012). The % is not probably syncing after (let's say power outage or system reboot basically) & on a slow connection. Screenshots: ![progress](http://i.imgur.com/VPfGe.png) ![total](http://i.imgur.com/oaByA.png) qBittorrent v3.0.2 Qt 4.8.2 Boost v1.5.0 Libtorrent v0.16.3.0 OS: ArchLinux 32bit P.S: Force recheck gives same results too :| so I guess i'm screwed? Let me know if more information is needed.
Author
Owner

@cdumez commented on GitHub (Oct 3, 2012):

What's the amount wasted? Unfortunately, it is the line right after the bottom of your screen shot. If the amount wasted is really high, then this would explain it.

@cdumez commented on GitHub (Oct 3, 2012): What's the amount wasted? Unfortunately, it is the line right after the bottom of your screen shot. If the amount wasted is really high, then this would explain it.
Author
Owner

@asamy commented on GitHub (Oct 3, 2012):

@cdumez hmm... i'm sorry for not showing that ._. I had closed the app but now I opened it again and it says 0 bytes wasted... same results still. (The "Downloaded" also reached the "Size" and yet it's still downloading...)
Also I remembered, it wasn't really high it was about 1 MB I think... is that "high"?

@asamy commented on GitHub (Oct 3, 2012): @cdumez hmm... i'm sorry for not showing that ._. I had closed the app but now I opened it again and it says 0 bytes wasted... same results still. (The "Downloaded" also reached the "Size" and yet it's still downloading...) Also I remembered, it wasn't really high it was about 1 MB I think... is that "high"?
Author
Owner

@Kervius commented on GitHub (Dec 8, 2012):

Win7/x64, qB 3.0.6 (but also seen it with qB 2.x):

progressbar-bug-qb306.png

The download is very large and very slow. Many shutdowns/reboots/hibernates. The state in image is shortly after "Force recheck". The top line is the total - five lines below are the sub-folders. The 94.8% seem to be correct. The 74.7% seems to be wrong. The per-folder percentage seem to be also correct.

@Kervius commented on GitHub (Dec 8, 2012): Win7/x64, qB 3.0.6 (but also seen it with qB 2.x): ![progressbar-bug-qb306.png](https://f.cloud.github.com/assets/2997827/2027/9c70e282-4177-11e2-8893-a238a2876c4b.png) The download is very large and very slow. Many shutdowns/reboots/hibernates. The state in image is shortly after "Force recheck". The top line is the total - five lines below are the sub-folders. The 94.8% seem to be correct. The 74.7% seems to be wrong. The per-folder percentage seem to be also correct.
Author
Owner

@Balls0fSteel commented on GitHub (Dec 5, 2013):

@Kervius Does the bug still happen at you?

@Balls0fSteel commented on GitHub (Dec 5, 2013): @Kervius Does the bug still happen at you?
Author
Owner

@Kervius commented on GitHub (Dec 5, 2013):

@GotDemBallsOfSteel, haven't seen it in a while. (But also were not downloading anything slow and huge recently.)

@Kervius commented on GitHub (Dec 5, 2013): @GotDemBallsOfSteel, haven't seen it in a while. (But also were not downloading anything slow and huge recently.)
Author
Owner

@Balls0fSteel commented on GitHub (Dec 5, 2013):

@Kervius IMO we should close this for now. If it happens to anyone we can pin it down and fix it, if it still exists.
@sledgehammer999 can be closed.

@Balls0fSteel commented on GitHub (Dec 5, 2013): @Kervius IMO we should close this for now. If it happens to anyone we can pin it down and fix it, if it still exists. @sledgehammer999 can be closed.
Author
Owner

@asamy commented on GitHub (Dec 5, 2013):

Well, I'm going to close it since I'm the issue starter. I guess we diagnosed the error now.

@asamy commented on GitHub (Dec 5, 2013): Well, I'm going to close it since I'm the issue starter. I guess we diagnosed the error now.
Author
Owner

@Balls0fSteel commented on GitHub (Dec 5, 2013):

@decltype Sorry, and thanks. I'm on a crusade to clean up our bugtracker. Thanks for the close/response. 👍

@Balls0fSteel commented on GitHub (Dec 5, 2013): @decltype Sorry, and thanks. I'm on a crusade to clean up our bugtracker. Thanks for the close/response. :+1:
Author
Owner

@sledgehammer999 commented on GitHub (Dec 9, 2013):

Yeah, I remember doing a fix on this in the 3.1.x series. Don't know if it affected this bug though 100%.

@sledgehammer999 commented on GitHub (Dec 9, 2013): Yeah, I remember doing a fix on this in the 3.1.x series. Don't know if it affected this bug though 100%.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#123
No description provided.