Torrents apparently silently disappeared, bunch of 0 byte resume files. #12754

New issue

Open

opened 2026-02-21 23:08:03 -05:00 by deekerman · 27 comments

deekerman commented 2026-02-21 23:08:03 -05:00

Owner

Copy link

Originally created by @mzso on GitHub (Jan 8, 2022).

qBittorrent & operating system versions

4.4.0
Win10 21h2 10.0.19044

What is the problem?

Because of the crashing issues and such I checked out the log.

And I noticed around 16 red items with items similar to this.
"2022. 01. 08. 21:02 - Unable to resume torrent '1eebce1a15e8003e773d19ee75228a8abc1b9acc'."

So I checked some of them out and all had 0 byte resume files.
(One also has a third "1d1ce6aca3cffbf3e3c39c4ed1e9009854069c8d.fastresume.IcgsbO" format file present, with an extra extension. Which was non zero, nut sure what this is)

I restored a couple resumes from an old backup and they worked fine. (Also I'm unlikely to have removed these torrents, because they from a tracker that I usually don't)

I can only guess that these got corrupted some time and QB didn't gave notice other than in the log, which one doesn't normally look at.
My best guess is that QB tried to write them but there was no space, and created 0 bytes files. (I sometimes run out of space when a torrents ends up on the wrong drive or such.)

Steps to reproduce

I don't know how it happens, I only have the guesses above

Additional context

This is really not nice. Torrents might silently disappear over time, without the user ever noticing. Unless someone actively watches for them.

I think QB should definitely display an alert if it fails to write some important files, so the user can resolve it before loss of data occurs. (I have no other ideas how the 0b files happened.)
In any ways it should try to write files if there's no space and shouldn't thrash the file before attempting to write.

QB should also display an alert if it fails to load torrents since the last session.
I guess this might require some more effort if it only loads .fastresume files from BT_backup, because at least the number of torrents need to be stored (preferably a list of them to be checked). Otherwise there's no way to tell when the torrents started failing.

All in all the accumulating detritus is not at all a good thing. I for one only check the log if I have noticeable problems, like right now with 4.4.0. But apparently I have been loosing torrents for a good while.

Log(s) & preferences file(s)

No response

Originally created by @mzso on GitHub (Jan 8, 2022). ### qBittorrent & operating system versions 4.4.0 Win10 21h2 10.0.19044 ### What is the problem? Because of the crashing issues and such I checked out the log. And I noticed around 16 red items with items similar to this. "2022. 01. 08. 21:02 - Unable to resume torrent '1eebce1a15e8003e773d19ee75228a8abc1b9acc'." So I checked some of them out and all had 0 byte resume files. (One also has a third "1d1ce6aca3cffbf3e3c39c4ed1e9009854069c8d.fastresume.IcgsbO" format file present, with an extra extension. Which was non zero, nut sure what this is) I restored a couple resumes from an old backup and they worked fine. (Also I'm unlikely to have removed these torrents, because they from a tracker that I usually don't) I can only guess that these got corrupted some time and QB didn't gave notice other than in the log, which one doesn't normally look at. My best guess is that QB tried to write them but there was no space, and created 0 bytes files. (I sometimes run out of space when a torrents ends up on the wrong drive or such.) ### Steps to reproduce I don't know how it happens, I only have the guesses above ### Additional context This is really not nice. Torrents might silently disappear over time, without the user ever noticing. Unless someone actively watches for them. I think QB should definitely display an alert if it fails to write some important files, so the user can resolve it before loss of data occurs. (I have no other ideas how the 0b files happened.) In any ways it should try to write files if there's no space and shouldn't thrash the file before attempting to write. QB should also display an alert if it fails to load torrents since the last session. I guess this might require some more effort if it only loads .fastresume files from BT_backup, because at least the number of torrents need to be stored (preferably a list of them to be checked). Otherwise there's no way to tell when the torrents started failing. All in all the accumulating detritus is not at all a good thing. I for one only check the log if I have noticeable problems, like right now with 4.4.0. But apparently I have been loosing torrents for a good while. ### Log(s) & preferences file(s) _No response_

deekerman added the

Data loss

label 2026-02-21 23:08:03 -05:00

deekerman commented 2026-02-21 23:08:08 -05:00

Author

Owner

Copy link

@mzso commented on GitHub (Jan 8, 2022):

Incidentally:
I realized while submitting this bug that I don't have a logfile enabled.
Since it had an appdata folder (but I'm using QB in portable mode), maybe inherited from when it was a local instance. I added the appropriate folder like this: ".\profile\qBittorrent\data\logs"
Which resulted in some strange behavior. Logs were created there, BUT QB also created empty folders corresponding to this path: .\profile\qBittorrent\data\logs\profile\qBittorrent\data\logs
Essentially "doubled" the relative path to the log, but never put anything there.

@mzso commented on GitHub (Jan 8, 2022): Incidentally: I realized while submitting this bug that I don't have a logfile enabled. Since it had an appdata folder (but I'm using QB in portable mode), maybe inherited from when it was a local instance. I added the appropriate folder like this: ".\profile\qBittorrent\data\logs\" Which resulted in some strange behavior. Logs were created there, BUT QB also created empty folders corresponding to this path: .\profile\qBittorrent\data\logs\profile\qBittorrent\data\logs\ Essentially "doubled" the relative path to the log, but never put anything there.

deekerman commented 2026-02-21 23:08:13 -05:00

Author

Owner

Copy link

@mzso commented on GitHub (Jan 8, 2022):

I examined relative paths a bit more and added .\profile\torrents to the "copy .torrent files to" feature. Which completely ceased functioning. Curiously the "finished torrents" folder also ceased functioning, even though I kept the absolute path that was there.

I guess QB sorely needs some improvements with relative paths.

EDIT
Scratch that. Now I notice that the last torrent copied was in 01-07 after midnight. Later torrents were not added, all of which are after I upgraded. So it seems like yet another bug of 4.4.0

EDIT2:
Downgrading to RC1 immediately made it working.

@mzso commented on GitHub (Jan 8, 2022): <s>I examined relative paths a bit more and added .\profile\torrents to the "copy .torrent files to" feature. Which completely ceased functioning. Curiously the "finished torrents" folder also ceased functioning, even though I kept the absolute path that was there. I guess QB sorely needs some improvements with relative paths.</s> **EDIT** Scratch that. Now I notice that the last torrent copied was in 01-07 after midnight. Later torrents were not added, all of which are after I upgraded. **_So it seems like yet another bug of 4.4.0_** **EDIT2:** Downgrading to RC1 immediately made it working.

deekerman commented 2026-02-21 23:08:16 -05:00

Author

Owner

Copy link

@Dnkhatri commented on GitHub (Jan 8, 2022):

Are you using MySQL in advanced settings?

@Dnkhatri commented on GitHub (Jan 8, 2022): Are you using MySQL in advanced settings?

deekerman commented 2026-02-21 23:08:16 -05:00

Author

Owner

Copy link

@mzso commented on GitHub (Jan 9, 2022):

So managed to dig up 81 out of 111 fastresume files from backups instead of the destroyed ones. All of these resumed seeding so plainly their resume files got overwritten with zero byte ones. (Apart from this I only had five that wouldn't resume because of missing files.)

@Dnkhatri commented on 2022. jan. 9. 03:21 CET:

Are you using MySQL in advanced settings?

No. What is that good for, by the way?

@mzso commented on GitHub (Jan 9, 2022): So managed to dig up 81 out of 111 fastresume files from backups instead of the destroyed ones. All of these resumed seeding so plainly their resume files got overwritten with zero byte ones. (Apart from this I only had five that wouldn't resume because of missing files.) [**@Dnkhatri**](https://github.com/Dnkhatri) commented on [2022. jan. 9. 03:21 CET](https://github.com/qbittorrent/qBittorrent/issues/15997#issuecomment-1008214763 "2022-01-09T02:21:30Z - Replied by Github Reply Comments"): > Are you using MySQL in advanced settings? No. What is that good for, by the way?

deekerman commented 2026-02-21 23:08:16 -05:00

Author

Owner

Copy link

@Dnkhatri commented on GitHub (Jan 9, 2022):

So managed to dig up 81 out of 111 fastresume files from backups instead of the destroyed ones. All of these resumed seeding so plainly their resume files got overwritten with zero byte ones. (Apart from this I only had five that wouldn't resume because of missing files.)

@Dnkhatri commented on 2022. jan. 9. 03:21 CET:

Are you using MySQL in advanced settings?

No. What is that good for, by the way?

That uses 1 sql file instead of 100s of fastresume files. [Its supposed to speed up starting and stopping of qbittorrent.
https://github.com/qbittorrent/qBittorrent/pull/14726

@Dnkhatri commented on GitHub (Jan 9, 2022): > So managed to dig up 81 out of 111 fastresume files from backups instead of the destroyed ones. All of these resumed seeding so plainly their resume files got overwritten with zero byte ones. (Apart from this I only had five that wouldn't resume because of missing files.) > > [**@Dnkhatri**](https://github.com/Dnkhatri) commented on [2022. jan. 9. 03:21 CET](https://github.com/qbittorrent/qBittorrent/issues/15997#issuecomment-1008214763): > > > Are you using MySQL in advanced settings? > > No. What is that good for, by the way? That uses 1 sql file instead of 100s of fastresume files. [Its supposed to speed up starting and stopping of qbittorrent. https://github.com/qbittorrent/qBittorrent/pull/14726

deekerman commented 2026-02-21 23:08:16 -05:00

Author

Owner

Copy link

@mzso commented on GitHub (Jan 9, 2022):

@Dnkhatri
I was not aware of that. Is it an alfa/beta feature? Does it run without much issue (particularly data loss)? And is switching to it trouble free?

@mzso commented on GitHub (Jan 9, 2022): @Dnkhatri I was not aware of that. Is it an alfa/beta feature? Does it run without much issue (particularly data loss)? And is switching to it trouble free?

deekerman commented 2026-02-21 23:08:16 -05:00

Author

Owner

Copy link

@mzso commented on GitHub (Jan 9, 2022):

Can it add new torrents if I copy torrent/resume files from a different instance?

@mzso commented on GitHub (Jan 9, 2022): Can it add new torrents if I copy torrent/resume files from a different instance?

deekerman commented 2026-02-21 23:08:16 -05:00

Author

Owner

Copy link

@Dnkhatri commented on GitHub (Jan 9, 2022):

Can it add new torrents if I copy torrent/resume files from a different instance?

No idea I just started using it when the 4.4 version dropped its an advanced alpha beta option so I don't know much about it. @glassez would be the one to ask.

@Dnkhatri commented on GitHub (Jan 9, 2022): > Can it add new torrents if I copy torrent/resume files from a different instance? No idea I just started using it when the 4.4 version dropped its an advanced alpha beta option so I don't know much about it. @glassez would be the one to ask.

deekerman commented 2026-02-21 23:08:17 -05:00

Author

Owner

Copy link

@LittleVulpix commented on GitHub (Jan 9, 2022):

My torrents simply disappear if I restart qbittorrent now. Reverting back to 4.3.9 fixes the problem.

@LittleVulpix commented on GitHub (Jan 9, 2022): My torrents simply disappear if I restart qbittorrent now. Reverting back to 4.3.9 fixes the problem.

deekerman commented 2026-02-21 23:08:17 -05:00

Author

Owner

Copy link

@glassez commented on GitHub (Jan 9, 2022):

My torrents simply disappear if I restart qbittorrent now.

Could you provide log for such a run?

@glassez commented on GitHub (Jan 9, 2022): > My torrents simply disappear if I restart qbittorrent now. Could you provide log for such a run?

deekerman commented 2026-02-21 23:08:17 -05:00

Author

Owner

Copy link

@mzso commented on GitHub (Jan 9, 2022):

@Dnkhatri commented on 2022. jan. 9. 14:23 CET:

Can it add new torrents if I copy torrent/resume files from a different instance?

No idea I just started using it when the 4.4 version dropped its an advanced alpha beta option so I don't know much about it. @glassez would be the one to ask.

I guess the crucial point is what happens when disk space runs out, which is an easy mistake to make. One would hope that something SQL based might handle that without undue dataloss.

@mzso commented on GitHub (Jan 9, 2022): [**@Dnkhatri**](https://github.com/Dnkhatri) commented on [2022. jan. 9. 14:23 CET](https://github.com/qbittorrent/qBittorrent/issues/15997#issuecomment-1008297497 "2022-01-09T13:23:23Z - Replied by Github Reply Comments"): > > Can it add new torrents if I copy torrent/resume files from a different instance? > > No idea I just started using it when the 4.4 version dropped its an advanced alpha beta option so I don't know much about it. [@glassez](https://github.com/glassez) would be the one to ask. I guess the crucial point is what happens when disk space runs out, which is an easy mistake to make. One would hope that something SQL based might handle that without undue dataloss.

deekerman commented 2026-02-21 23:08:17 -05:00

Author

Owner

Copy link

@LittleVulpix commented on GitHub (Jan 9, 2022):

My torrents simply disappear if I restart qbittorrent now.

Could you provide log for such a run?

I checked the log - there is a single message related to this (upon startup) that says:

(C) 2022-01-10T02:57:42 - Unable to resume torrent 'b6434b6ab1bf60c21f6fd441d56575b62703c008'.

I checked the fastresume file, it's quite large; almost 754MB.

Not sure if it matters, but I made this as torrent v2 (also with bittorrent v4.4.0).

Another annoying thing is - when I do torrent recheck, it uses up all of my computer's available memory.
It helps if I use sysinternals' rammap to "empty working sets", then it fills back up and starts swapping horribly, causing slower hashing speeds and load on the disk hosting pagefile.
Does not happen on 4.3.9 with the same settings. Moreover, 4.3.9 is much faster (about 3x faster - ~650MB/s vs ~211MB/s. I kind of expect this due to the new hash algo of torrent v2 but the memleak is not nice)

Every drop is after I press the "empty working sets" function in rammap.

@LittleVulpix commented on GitHub (Jan 9, 2022): > > My torrents simply disappear if I restart qbittorrent now. > > Could you provide log for such a run? I checked the log - there is a single message related to this (upon startup) that says: `(C) 2022-01-10T02:57:42 - Unable to resume torrent 'b6434b6ab1bf60c21f6fd441d56575b62703c008'.` I checked the fastresume file, it's quite large; almost 754MB. Not sure if it matters, but I made this as torrent v2 (also with bittorrent v4.4.0). Another annoying thing is - when I do torrent recheck, it uses up all of my computer's available memory. It helps if I use sysinternals' rammap to "empty working sets", then it fills back up and starts swapping horribly, causing slower hashing speeds and load on the disk hosting pagefile. Does not happen on 4.3.9 with the same settings. Moreover, 4.3.9 is much faster (about 3x faster - ~650MB/s vs ~211MB/s. I kind of expect this due to the new hash algo of torrent v2 but the memleak is not nice)  Every drop is after I press the "empty working sets" function in rammap.

deekerman commented 2026-02-21 23:08:17 -05:00

Author

Owner

Copy link

@mzso commented on GitHub (Jan 9, 2022):

@littlevulpix
"about 3x faster - ~650MB/s vs ~211MB/s. I kind of expect this due to the new hash algo of torrent v2 but the memleak is not nice"
I don't think has algorithms are likely to effect transfer speeds. But if there's a lot of swapping it might.

@mzso commented on GitHub (Jan 9, 2022): @littlevulpix "about 3x faster - ~650MB/s vs ~211MB/s. I kind of expect this due to the new hash algo of torrent v2 but the memleak is not nice" I don't think has algorithms are likely to effect transfer speeds. But if there's a lot of swapping it might.

deekerman commented 2026-02-21 23:08:17 -05:00

Author

Owner

Copy link

@LittleVulpix commented on GitHub (Jan 10, 2022):

@LittleVulpix "about 3x faster - ~650MB/s vs ~211MB/s. I kind of expect this due to the new hash algo of torrent v2 but the memleak is not nice" I don't think has algorithms are likely to effect transfer speeds. But if there's a lot of swapping it might.

No no, not transfer speed. Hashing speed.

@LittleVulpix commented on GitHub (Jan 10, 2022): > @LittleVulpix "about 3x faster - ~650MB/s vs ~211MB/s. I kind of expect this due to the new hash algo of torrent v2 but the memleak is not nice" I don't think has algorithms are likely to effect transfer speeds. But if there's a lot of swapping it might. No no, not transfer speed. Hashing speed.

deekerman commented 2026-02-21 23:08:17 -05:00

Author

Owner

Copy link

@ted423 commented on GitHub (Apr 3, 2023):

same here qb 4.5.2 on ubuntu

apt list --installed|grep qb

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

qbittorrent/jammy,now 1:4.5.2.99~202302282217-7873-97853f31f~ubuntu22.04.1 amd64 [已安装]

@ted423 commented on GitHub (Apr 3, 2023): same here qb 4.5.2 on ubuntu    ``` apt list --installed|grep qb WARNING: apt does not have a stable CLI interface. Use with caution in scripts. qbittorrent/jammy,now 1:4.5.2.99~202302282217-7873-97853f31f~ubuntu22.04.1 amd64 [已安装] ```

deekerman commented 2026-02-21 23:08:17 -05:00

Author

Owner

Copy link

@ted423 commented on GitHub (Apr 3, 2023):

i think qb may show error stat and let user recheck torrent

@ted423 commented on GitHub (Apr 3, 2023): i think qb may show error stat and let user recheck torrent

deekerman commented 2026-02-21 23:08:17 -05:00

Author

Owner

Copy link

@ted423 commented on GitHub (Apr 3, 2023):

i delete the 0b file(500+),and seems the torrent lost in qb and not show in the log

@ted423 commented on GitHub (Apr 3, 2023): i delete the 0b file(500+),and seems the torrent lost in qb and not show in the log

deekerman commented 2026-02-21 23:08:17 -05:00

Author

Owner

Copy link

@ted423 commented on GitHub (Apr 3, 2023):

the gui can't add such torrent (seems too long)
so I and to watched folder

and get this

@ted423 commented on GitHub (Apr 3, 2023): the gui can't add such torrent (seems too long) so I and to watched folder  and get this 

deekerman commented 2026-02-21 23:08:17 -05:00

Author

Owner

Copy link

@mzso commented on GitHub (Apr 3, 2023):

@ted423 Not sure what you're trying to accomplish here. Of course QB won't load 0B fastresume files, because they have no data.

The automatically add torrents setting is to add new downloads via .torrent files. Fastresume is only used internally.

@mzso commented on GitHub (Apr 3, 2023): @ted423 Not sure what you're trying to accomplish here. Of course QB won't load 0B fastresume files, because they have no data. The automatically add torrents setting is to add new downloads via .torrent files. Fastresume is only used internally.

deekerman commented 2026-02-21 23:08:17 -05:00

Author

Owner

Copy link

@ted423 commented on GitHub (Apr 4, 2023):

lost more than 500 torrent. you can check that only in logs.
For torrent management, I want some way to know those thing in webui or some other way

@ted423 commented on GitHub (Apr 4, 2023): lost more than 500 torrent. you can check that only in logs. For torrent management, I want some way to know those thing in webui or some other way

deekerman commented 2026-02-21 23:08:17 -05:00

Author

Owner

Copy link

@ted423 commented on GitHub (Apr 4, 2023):

I need to check which torrent are disappeared, and I found this way

the gui can't add such torrent (seems too long) so I and to watched folder

and get this

@ted423 commented on GitHub (Apr 4, 2023): I need to check which torrent are disappeared, and I found this way > the gui can't add such torrent (seems too long) so I and to watched folder  > > and get this 

deekerman commented 2026-02-21 23:08:18 -05:00

Author

Owner

Copy link

@ted423 commented on GitHub (Apr 10, 2023):

I need to check which torrent are disappeared, and I found this way

the gui can't add such torrent (seems too long) so I and to watched folder
and get this

it seems need copy all torrent out that folder to add watched, my .torrent file all lost in that folder and make all torrent 0B

@ted423 commented on GitHub (Apr 10, 2023): > I need to check which torrent are disappeared, and I found this way > > > the gui can't add such torrent (seems too long) so I and to watched folder  > > and get this  it seems need copy all torrent out that folder to add watched, my .torrent file all lost in that folder and make all torrent 0B

deekerman commented 2026-02-21 23:08:18 -05:00

Author

Owner

Copy link

@SanderBouwhuis commented on GitHub (Apr 28, 2023):

@ted423
This all sounds very scary! Is the cause known? Or is your problem no longer occurring?

@SanderBouwhuis commented on GitHub (Apr 28, 2023): @ted423 This all sounds very scary! Is the cause known? Or is your problem no longer occurring?

deekerman commented 2026-02-21 23:08:18 -05:00

Author

Owner

Copy link

@ted423 commented on GitHub (May 3, 2023):

@ted423 This all sounds very scary! Is the cause known? Or is your problem no longer occurring?

It seems happened in half a year ago, accroding the file's data.

The follow-up situation is after trying to restore these torrent files, I post here to avoid detours for others

@ted423 commented on GitHub (May 3, 2023): > @ted423 This all sounds very scary! Is the cause known? Or is your problem no longer occurring? It seems happened in half a year ago, accroding the file's data. The follow-up situation is after trying to restore these torrent files, I post here to avoid detours for others

deekerman commented 2026-02-21 23:08:18 -05:00

Author

Owner

Copy link

@qBittUser commented on GitHub (Mar 26, 2025):

Can anyone reproduce with latest version?

Does Execution log tab (you can open qBit>View>Logs to enable it) show if qBit failed to load any previous sessions torrent transfers?

@qBittUser commented on GitHub (Mar 26, 2025): Can anyone reproduce with latest version? Does `Execution log` tab (you can open qBit>View>Logs to enable it) show if qBit failed to load any previous sessions torrent transfers?

deekerman commented 2026-02-21 23:08:18 -05:00

Author

Owner

Copy link

@ted423 commented on GitHub (Mar 26, 2025):

I guess it's a problem caused by an earlier version upgrade

@ted423 commented on GitHub (Mar 26, 2025): I guess it's a problem caused by an earlier version upgrade

deekerman commented 2026-02-21 23:08:18 -05:00

Author

Owner

Copy link

@mzso commented on GitHub (Aug 20, 2025):

@ted423 This all sounds very scary! Is the cause known? Or is your problem no longer occurring?

This issue most likely happens when running out of disk space. QB tries to write these data files without checking, and it fails, so the data gets destroyed. And you'll have no sign of it until you notice missing torrents in the client.

@mzso commented on GitHub (Aug 20, 2025): > [@ted423](https://github.com/ted423) This all sounds very scary! Is the cause known? Or is your problem no longer occurring? This issue most likely happens when running out of disk space. QB tries to write these data files without checking, and it fails, so the data gets destroyed. And you'll have no sign of it until you notice missing torrents in the client.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

v5_2_x

v5_1_x

debian

v5_0_x

v4_6_x

v4_5_x

v4_4_x

v4_3_x

v4_2_x

v4_1_x

v4_0_x

v3_3_x

v3_2_x

v3_1_x

v3_0_x

search_encoding_windows

v2_9_x

release-5.1.4

release-5.1.3

release-5.1.2

release-5.1.1

release-5.1.0

release-5.0.5

release-5.0.4

release-5.1.0rc1

release-5.1.0beta1

release-5.0.3

release-5.0.2

release-5.0.1

release-5.0.0

release-4.6.7

release-5.0.0rc1

release-4.6.6

release-4.6.5

release-4.6.4

release-5.0.0beta1

release-4.6.3

release-4.6.2

release-4.6.1

release-4.6.0

release-4.6.0rc2

release-4.5.5

release-4.6.0rc1

release-4.6.0beta1

release-4.5.4

release-4.6.0alpha1

release-4.5.3

release-4.5.2

release-4.5.1

release-4.5.0

release-4.5.0beta1

release-4.4.5

release-4.4.4

release-4.4.3.1

release-4.4.3

release-4.4.2

release-4.4.1

release-4.4.0

release-4.3.9

release-4.4.0rc1

release-4.3.8

release-4.4.0beta3

release-4.3.7

release-4.4.0beta2

release-4.4.0beta1

release-4.3.6

release-4.3.5

release-4.3.4.1

release-4.3.4

release-4.3.3

release-4.3.2

release-4.3.1

release-4.3.0.1

release-4.3.0

release-4.2.5

release-4.2.4

release-4.2.3

release-4.2.2

release-4.2.1

release-4.2.0

release-4.1.9.1

release-4.1.9

release-4.1.8

release-4.1.7

release-4.1.6

release-4.1.5

release-4.1.4

release-4.1.3

release-4.1.2

release-4.1.1

release-4.1.0

release-4.0.4

release-4.0.3

release-4.0.2

release-4.0.1

release-4.0.0

release-3.3.16

release-3.3.15

release-3.3.14

release-3.3.13

release-3.3.12

release-3.3.11

release-3.3.10

release-3.3.9

release-3.3.8

release-3.3.7

release-3.3.6

release-3.3.5

release-3.3.4

release-3.3.3

release-3.3.2

release-3.3.1

release-3.3.0

release-3.2.5

release-3.2.4

release-3.2.3

release-3.2.2

release-3.2.1

release-3.2.0

release-3.1.12

release-3.1.11

release-3.1.10

release-3.1.9.2

release-3.1.9.1

release-3.1.9

release-3.1.8

release-3.1.7

release-3.1.6

release-3.1.5

release-3.1.4

release-3.1.3

release-3.1.2

release-3.1.1

release-3.1.0

release-3.0.11

release-3.0.10

release-3.0.9

release-3.0.8

release-3.0.7

release-3.0.6

release-3.0.5

release-3.0.4

release-3.0.3

release-3.0.2

release-3.0.1

release-3.0.0

release-2.9.11

release-2.9.10

release-2.9.9

release-2.9.8

release-2.9.7

release-2.9.6

release-2.9.5

release-2.9.4

release-2.9.3

release-2.9.0

release-2.8.5

release-2.8.4

release-2.8.3

release-2.8.2

release-2.7.1

release-2.7.0

release-2.6.9

release-2.6.8

release-2.6.7

release-2.6.5

release-2.6.4

release-2.6.3

release-2.6.2

release-2.6.1

release-2.6.0

release-2.5.5

release-2.5.4

release-2.5.3

release-2.5.2

release-2.5.0

release-2.5.0rc1

release-2.4.11

release-2.5.0beta6

release-2.5.0beta5

release-2.5.0beta3

release-2.4.10

release-2.4.8

release-2.5.0beta2

release-2.5.0beta1

release-2.4.6

release-2.4.4

release-2.4.2

release-2.4.0

release-2.4.0rc3

release-2.4.0rc1

release-2.4.0beta3

release-2.4.0beta1

release-2.3.1

release-2.3.0

release-2.3.0rc6

release-2.2.11

release-2.3.0rc5

release-2.2.10

release-2.2.9

release-2.2.8

release-2.2.6

release-2.2.5

release-2.2.3

release-2.2.2

release-2.2.1

release-2.2.0

release-2.1.6

release-2.1.4

release-2.1.2

release-2.1.1

release-2.1.0

release-2.0.7

release-2.0.6

release-2.0.5

release-2.0.3

release-2.0.2

release-2.0.0

release-2.0.0rc6

release-2.0.0rc2

release-1.5.6

release-1.5.4

release-1.5.3

release-1.5.0

release-1.5.0rc5

release-1.5.0rc4

release-1.5.0rc3

release-1.5.0rc1

release-1.5.0beta4

release-1.5.0beta3

release-1.5.0beta2

release-1.5.0beta1

release-1.4.1

release-1.4.0

release-1.4.0rc2

release-1.4.0rc1

release-1.3.5

release-1.4.0beta3

release-1.3.4

release-1.3.3

release-1.3.1

release-1.3.0

release-1.2.1

release-1.2.0rc1

release-1.2.0beta6

release-1.1.4

release-1.2.0beta5

release-1.1.3

release-1.2.0beta3

release-1.1.2

release-1.2.0beta2

release-1.1.1

release-1.2.0beta1

release-1.1.0

release-1.1.0rc2

release-1.1.0rc1

release-1.1.0beta3

release-1.1.0beta2

release-1.0.0

release-1.0.0rc11

release-1.0.0rc10

release-1.0.0rc9

release-1.0.0rc8

release-1.0.0rc7

release-1.0.0rc6

release-1.0.0rc5

release-1.0.0rc4

release-1.0.0rc3

release-0.9.3

release-0.9.2

Labels

Clear labels   

Accessibility

  

AppImage

  

Bounty

  

Build system

  

CI

  

Can't reproduce

  

Code cleanup

  

Confirmed bug

  

Confirmed bug

  

Core

  

Crash

  

Data loss

  

Discussion

  

Docker

  

Documentation

  

Duplicate

  

Feature

  

Feature request

  

Feature request

  

Feature request

  

Filters

  

Flatpak

  

GUI

  

Has workaround

  

I2P

  

Invalid

  

Libtorrent

  

Look and feel

  

Meta

  

NSIS

  

Network

  

Not an issue

  

OS: *BSD

  

OS: Linux

  

OS: Windows

  

OS: macOS

  

PPA

  

Performance

  

Project management

  

Proxy/VPN

  

Qt bugs

  

Qt6 compat

  

RSS

  

Search engine

  

Security

  

Temp folder

  

Themes

  

Translations

  

Triggers

  

Waiting diagnosis

  

Waiting info

  

Waiting upstream

  

Waiting web implementation

  

Watched folders

  

WebAPI

  

WebUI

  

autoCloseOldIssue

No labels

Accessibility

AppImage

Bounty

Build system

CI

Can't reproduce

Code cleanup

Confirmed bug

Confirmed bug

Core

Crash

Data loss

Discussion

Docker

Documentation

Duplicate

Feature

Feature request

Feature request

Feature request

Filters

Flatpak

GUI

Has workaround

I2P

Invalid

Libtorrent

Look and feel

Meta

NSIS

Network

Not an issue

OS: *BSD

OS: Linux

OS: Windows

OS: macOS

PPA

Performance

Project management

Proxy/VPN

Qt bugs

Qt6 compat

RSS

Search engine

Security

Temp folder

Themes

Translations

Triggers

Waiting diagnosis

Waiting info

Waiting upstream

Waiting web implementation

Watched folders

WebAPI

WebUI

autoCloseOldIssue

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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#12754

No description provided.