Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Progress bar possible bug #11189

Open
Timsonrobl opened this issue Sep 3, 2019 · 0 comments

Comments

@Timsonrobl
Copy link

commented Sep 3, 2019

qBittorrent 4.1.7 on Windows 10 x64
Using HDD (can be relevant)

There seems to be reproducible strange behavior, possible visual (or logical) bug.
It happens under following conditions with good reproducibility (every time):

  1. Downloading big files (30+gb) with many pieces (4000+). Under this conditions bars in progress bar in general tab have less than 1 pixel per piece scale.
  2. Starting download with "Download in sequential order" and "Download first and last pieces" ON.
  3. Starting download with high speed (35 MB/s+). This behavior never happened to me on speeds <10MB/s
    At this point in progress bar a hole will start to appear. It will always be after first pieces affected by "Download first and last pieces" priority. It looks like this:
    Аннотация 2019-09-03 210023
    At first I thought of it as normal indication as some pieces are getting stuck on slow seeds. But it's still strange since this "hole" will almost always have the same distribution picture of "missing" pieces.
  4. Pause the download and set speed limit to slower than 10 MB/s
  5. Unpause download.
    At this point the download will continue on but the "hole' will remain.
  6. Pause the download again. Wait some time to make sure all data transfer ceased.
  7. Exit qBittorent
  8. Restart qBittorent
  9. Unpause the download

After this there the "hole" will start to disappear rapidly. The status would be "Downloading" but the speed will remain very low (under 70 Kb/s) but despite this the progress bar will indicate huge progress (like 100 MB/s) until the "hole" is gone completely. After the hole is gone the Download speed would rapidly go up to the limit and the download task would continue normally with no issues. Sometime the hole would disappear over 5-10 seconds but sometimes it would do it almost instantaneously.

I'm not sure what this observations indicate but something is not right. Is it a visual bug in UI or this pieces really remain incomplete until client restart? Note that just pausing and unpausing between steps 6 and 7 will have no result. I can reproduce it every time I download big enough torrent with a swarm that can support very high downloading speed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.