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

All torrents seeding/downloading stop once global upload amount reaches ~1.986TB #13003

Open
userix opened this issue Jun 11, 2020 · 4 comments

Comments

@userix
Copy link

userix commented Jun 11, 2020

Please provide the following information

qBittorrent version and Operating System

(type here)
4.2.5 windows 7 64-bit (6.1.760x)

If on linux, libtorrent-rasterbar and Qt version

(type here)

What is the problem

overall Seeding seems to completely stop for all torrents once the global upload amount reaches ~1.986TB. I have ~20 torrents being seeded and all of them competely stops, it still indicates "seeding" and not "stalled", so it should be continuing to seed. I have to force close the app process via task manager and then open qbittorrent program to have all torrent seed again.

What is the expected behavior

Seeding should continue indefinitely and shouldn't stop when global upload

Steps to reproduce

Seed any torrent/s until the global upload data amount reaches ~1.916TB

Extra info(if any)

(type here)

@xavier2k6
Copy link
Member

Is that info from the statistics window?

@thalieht
Copy link
Contributor

I think he means upload that much in one session but someone with a huge connection/never closes qBt would have to verify.

@xavier2k6
Copy link
Member

I think he means upload that much in one session but someone with a huge connection/never closes qBt would have to verify.

If only......lol

What about setting limit share ratio to Set no share limit? for those seeding torrents.

@FranciscoPombal
Copy link
Member

FranciscoPombal commented Jun 23, 2020

I noticed OP mentions two different numbers - 1.986 and 1.916 TiB.

1.9x6 TiB in KiB is suspiciously close to signed int32 max (although 1.986 is actually over that). Could it be an overflow issue somewhere where data is counted in KiB?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants