starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

crash when not enough space #15875

New issue

Open

opened 2026-02-22 02:34:53 -05:00 by deekerman · 19 comments

deekerman commented

2026-02-22 02:34:53 -05:00

Owner

Originally created by @Obegg on GitHub (Jun 28, 2024).

qBittorrent & operating system versions

qBittorrent-CI_Windows-x64_libtorrent-2.0.10-setup (https://github.com/qbittorrent/qBittorrent/actions/runs/9710064895)
Qt: 6.7.0
Libtorrent: 2.0.10.0
Boost: 1.85.0
OpenSSL: 3.3.1
zlib: 1.3.1

What is the problem?

if there's not enough storage qbit will crash

Steps to reproduce

download torrent to a low storage hard drive

Additional context

I changed every title on the log file to "GitHub" just for privacy reasons

Log(s) & preferences file(s)

(N) 2024-06-28T21:28:57 - Torrent download finished. Torrent: "GitHub"
(N) 2024-06-28T21:28:57 - Torrent reached the share ratio limit. Removing torrent. Torrent: "GitHub".
(N) 2024-06-28T21:30:11 - Removed torrent. Torrent: "GitHub"
(N) 2024-06-28T21:33:46 - Enqueued torrent move. Torrent: "GitHub". Source: "G:\GitHub". Destination: "F:\GitHub"
(N) 2024-06-28T21:33:46 - Start moving torrent. Torrent: "GitHub". Destination: "F:\GitHub"
(W) 2024-06-28T21:34:24 - Failed to move torrent. Torrent: "GitHub". Source: "G:\GitHub". Destination: "F:\GitHub". Reason: "GitHub storage move failed. file_copy (G:\GitHub\GitHub\GitHub): There is not enough space on the disk"
(N) 2024-06-28T21:34:34 - Enqueued torrent move. Torrent: "GitHub". Source: "G:\GitHub". Destination: "F:\GitHub"
(N) 2024-06-28T21:34:34 - Start moving torrent. Torrent: "GitHub". Destination: "F:\GitHub"
(N) 2024-06-28T21:34:34 - Failed to enqueue torrent move. Torrent: "GitHub". Source: "G:\GitHub". Destination: "F:\GitHub". Reason: torrent is currently moving to the destination
(W) 2024-06-28T21:34:35 - Failed to move torrent. Torrent: "GitHub". Source: "G:\GitHub". Destination: "F:\GitHub". Reason: "GitHub storage move failed. file_copy (G:\GitHub\GitHub\GitHub): There is not enough space on the disk"
(N) 2024-06-28T21:34:36 - Torrent reached the share ratio limit. Removing torrent. Torrent: "GitHub".
(N) 2024-06-28T21:34:36 - Torrent download finished. Torrent: "GitHub"
(N) 2024-06-28T21:40:20 - qBittorrent v5.0.0beta1 started. Process ID: 14208

Originally created by @Obegg on GitHub (Jun 28, 2024). ### qBittorrent & operating system versions qBittorrent-CI_Windows-x64_libtorrent-2.0.10-setup (https://github.com/qbittorrent/qBittorrent/actions/runs/9710064895) Qt: 6.7.0 Libtorrent: 2.0.10.0 Boost: 1.85.0 OpenSSL: 3.3.1 zlib: 1.3.1 ### What is the problem? if there's not enough storage qbit will crash ### Steps to reproduce 1. download torrent to a low storage hard drive ### Additional context I changed every title on the log file to "GitHub" just for privacy reasons ### Log(s) & preferences file(s) ``` (N) 2024-06-28T21:28:57 - Torrent download finished. Torrent: "GitHub" (N) 2024-06-28T21:28:57 - Torrent reached the share ratio limit. Removing torrent. Torrent: "GitHub". (N) 2024-06-28T21:30:11 - Removed torrent. Torrent: "GitHub" (N) 2024-06-28T21:33:46 - Enqueued torrent move. Torrent: "GitHub". Source: "G:\GitHub". Destination: "F:\GitHub" (N) 2024-06-28T21:33:46 - Start moving torrent. Torrent: "GitHub". Destination: "F:\GitHub" (W) 2024-06-28T21:34:24 - Failed to move torrent. Torrent: "GitHub". Source: "G:\GitHub". Destination: "F:\GitHub". Reason: "GitHub storage move failed. file_copy (G:\GitHub\GitHub\GitHub): There is not enough space on the disk" (N) 2024-06-28T21:34:34 - Enqueued torrent move. Torrent: "GitHub". Source: "G:\GitHub". Destination: "F:\GitHub" (N) 2024-06-28T21:34:34 - Start moving torrent. Torrent: "GitHub". Destination: "F:\GitHub" (N) 2024-06-28T21:34:34 - Failed to enqueue torrent move. Torrent: "GitHub". Source: "G:\GitHub". Destination: "F:\GitHub". Reason: torrent is currently moving to the destination (W) 2024-06-28T21:34:35 - Failed to move torrent. Torrent: "GitHub". Source: "G:\GitHub". Destination: "F:\GitHub". Reason: "GitHub storage move failed. file_copy (G:\GitHub\GitHub\GitHub): There is not enough space on the disk" (N) 2024-06-28T21:34:36 - Torrent reached the share ratio limit. Removing torrent. Torrent: "GitHub". (N) 2024-06-28T21:34:36 - Torrent download finished. Torrent: "GitHub" (N) 2024-06-28T21:40:20 - qBittorrent v5.0.0beta1 started. Process ID: 14208 ```

deekerman added the

Crash

Waiting info

Waiting diagnosis

labels

2026-02-22 02:34:53 -05:00

deekerman commented

2026-02-22 02:34:58 -05:00

Author

Owner

@thalieht commented on GitHub (Jun 28, 2024):

If you want to help by providing a stacktrace https://github.com/qbittorrent/qBittorrent/issues/20869#issuecomment-2168749126

@thalieht commented on GitHub (Jun 28, 2024): If you want to help by providing a stacktrace https://github.com/qbittorrent/qBittorrent/issues/20869#issuecomment-2168749126

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@stalkerok commented on GitHub (Jun 28, 2024):

Can't reproduce, client reported insufficient disk space, didn't crash out. Need more information.

@stalkerok commented on GitHub (Jun 28, 2024): Can't reproduce, client reported insufficient disk space, didn't crash out. Need more information.

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@Obegg commented on GitHub (Jun 28, 2024):

If you want to help by providing a stacktrace #20869 (comment)

I think you should it add to the wiki because I did want to attach a more detailed crash report, but couldn't find anything on the wiki.
Better yet - add it to the issue template on GitHub.

Can't reproduce, client reported insufficient disk space, didn't crash out. Need more information.

Mmm, maybe try setting a Default Save Path to one location and enable the Use another path for incomplete torrents and set it a different hard drive?
I think the Default Save Path drive should be low space in order to reproduce it.
Also maybe enable Pre-allocate disk space for all files?
Also maybe enable Seeding Limits to Remove torrent when (the 3 options) are 0?
Other than that I just maximized every value possible in the Advanced tab, but I don't think those settings are the reason qbit crashes, the only time (well, two times) qbit crashed (while I was using the CI windows build) was when I had low storage.

Anyway - I "downgraded" to the more stable 4.6.5 version, because I noticed that some downloads did not move from the first hard drive to the second hard drive (when qbit crashed those two times when low I had low storage space).
I also cleared some space after I opened this issue so I'll need to re-fill the hard drive in order to reproduce it.
So I'm not sure if I should close this issue or keep it open till someone (other than me) reproduces it.

@Obegg commented on GitHub (Jun 28, 2024): > If you want to help by providing a stacktrace [#20869 (comment)](https://github.com/qbittorrent/qBittorrent/issues/20869#issuecomment-2168749126) I think you should it add to the [wiki](https://github.com/qbittorrent/qBittorrent/wiki) because I did want to attach a more detailed crash report, but couldn't find anything on the wiki. Better yet - add it to the issue template on GitHub. > Can't reproduce, client reported insufficient disk space, didn't crash out. Need more information. Mmm, maybe try setting a `Default Save Path` to one location and enable the `Use another path for incomplete torrents` and set it a different hard drive? I think the `Default Save Path` drive should be low space in order to reproduce it. Also maybe enable `Pre-allocate disk space for all files`? Also maybe enable `Seeding Limits` to `Remove torrent` when (the 3 options) are `0`? Other than that I just maximized every value possible in the `Advanced` tab, but I don't think those settings are the reason qbit crashes, the only time (well, two times) qbit crashed (while I was using the CI windows build) was when I had low storage. Anyway - I "downgraded" to the more stable 4.6.5 version, because I noticed that some downloads did not move from the first hard drive to the second hard drive (when qbit crashed those two times when low I had low storage space). I also cleared some space after I opened this issue so I'll need to re-fill the hard drive in order to reproduce it. So I'm not sure if I should close this issue or keep it open till someone (other than me) reproduces it.

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@stalkerok commented on GitHub (Jun 29, 2024):

Need clear steps to reproduce, without maybe.

@stalkerok commented on GitHub (Jun 29, 2024): Need clear steps to reproduce, without maybe.

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Jun 30, 2024):

@Obegg In any case it would be most helpful & highly appreciated if you could try to produce a valid stack trace from instructions/method in https://github.com/qbittorrent/qBittorrent/issues/20869#issuecomment-2168749126

@xavier2k6 commented on GitHub (Jun 30, 2024): @Obegg In any case it would be most helpful & highly appreciated if you could try to produce a valid stack trace from instructions/method in https://github.com/qbittorrent/qBittorrent/issues/20869#issuecomment-2168749126

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@zwei7 commented on GitHub (Jul 15, 2024):

Got this problem too with qbittorrent v4.6.5
To recreate:

Disable pre-allocating space for files.
Have 4 gigs of free space.
Set up RSS feed to auto download torrents, 30+ of them, each 1-8000 MB large.
Wait for your disk to reach 0 MB free space.
Then wait over the course of 24 hours.
Start interacting with your qbittorrent by highlighting/selecting torrents you downloaded, maybe rename the torrent title with an f2. Don't actually rename any of the files downloaded since an insufficient free space error will occur. After 50-100 of these benign selections and renaming actions, qbittorent will crash. One time I right clicked the qbittorent icon in the system tray (near the clock on the bottom right, Windows 10) and it immediately crashed.

On a related note about recreating the insufficient space problem, if you download 2 differently named torrents, let's say ABC and XYZ and their files and folder structures are identical, they will fight and try to overwrite one another. Fighting causes Qbittorrent to have a harddrive memory leak (not ram leak, hard drive leak) and use up all your free space. The only way to fix it is to restart qbittorrent and your free space will increase back to sane levels, then you delete either torrent ABC or XYZ or both to stop the hard drive memory leak.

This leak leads to no free space and leads to a crash.

@zwei7 commented on GitHub (Jul 15, 2024): Got this problem too with qbittorrent v4.6.5 To recreate: 1. Disable pre-allocating space for files. 2. Have 4 gigs of free space. 3. Set up RSS feed to auto download torrents, 30+ of them, each 1-8000 MB large. 4. Wait for your disk to reach 0 MB free space. 5. Then wait over the course of 24 hours. 6. Start interacting with your qbittorrent by highlighting/selecting torrents you downloaded, maybe rename the torrent title with an f2. Don't actually rename any of the files downloaded since an insufficient free space error will occur. After 50-100 of these benign selections and renaming actions, qbittorent will crash. One time I right clicked the qbittorent icon in the system tray (near the clock on the bottom right, Windows 10) and it immediately crashed. On a related note about recreating the insufficient space problem, if you download 2 differently named torrents, let's say ABC and XYZ and their files and folder structures are identical, they will fight and try to overwrite one another. Fighting causes Qbittorrent to have a harddrive memory leak (not ram leak, hard drive leak) and use up all your free space. The only way to fix it is to restart qbittorrent and your free space will increase back to sane levels, then you delete either torrent ABC or XYZ or both to stop the hard drive memory leak. This leak leads to no free space and leads to a crash.

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Jul 15, 2024):

@zwei7 see https://github.com/qbittorrent/qBittorrent/issues/21008#issuecomment-2198499842

@xavier2k6 commented on GitHub (Jul 15, 2024): @zwei7 see https://github.com/qbittorrent/qBittorrent/issues/21008#issuecomment-2198499842

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Aug 14, 2024):

@Obegg @zwei7 Ping!

@xavier2k6 commented on GitHub (Aug 14, 2024): @Obegg @zwei7 Ping!

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@Obegg commented on GitHub (Aug 14, 2024):

@Obegg @zwei7 Ping!

As I mentioned in https://github.com/qbittorrent/qBittorrent/issues/21008#issuecomment-2197643620 - I no longer use the unstable master release, I use the latest stable release which is 4.6.5, and I would also need to fill up the disk so this would be even more likely to happen in the future

@Obegg commented on GitHub (Aug 14, 2024): > @Obegg @zwei7 Ping! As I mentioned in https://github.com/qbittorrent/qBittorrent/issues/21008#issuecomment-2197643620 - I no longer use the unstable master release, I use the latest stable release which is 4.6.5, and I would also need to fill up the disk so this would be even more likely to happen in the future

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@zwei7 commented on GitHub (Aug 17, 2024):

Using the same qbittorrent v4.6.5 client I was able to reproduce this crash.

I think it might be due to the fact that I have like +700 RSS download rules and +25k torrents as well.

But this time I have 400-500 GB of free space (the torrents never created a 0 GB no free space scenario) and it still crashes if you wait long enough and interact with it (by opening qbittorent from the bottom right tray) as mentioned in my earlier post on July 15 2024.

@zwei7 commented on GitHub (Aug 17, 2024): Using the same qbittorrent v4.6.5 client I was able to reproduce this crash. I think it might be due to the fact that I have like +700 RSS download rules and +25k torrents as well. But this time I have 400-500 GB of free space (the torrents never created a 0 GB no free space scenario) and it still crashes if you wait long enough and interact with it (by opening qbittorent from the bottom right tray) as mentioned in my earlier post on July 15 2024.

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Aug 23, 2024):

@zwei7 If you can reproduce the crash with latest stable 4.6.6 then it would be most beneficial to us to obtain a stack trace/crash report with symbols.

@xavier2k6 commented on GitHub (Aug 23, 2024): @zwei7 If you can reproduce the crash with latest stable 4.6.6 then it would be most beneficial to us to obtain a stack trace/crash report with symbols.

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@zwei7 commented on GitHub (Aug 23, 2024):

Tried Version 4.6.6 and is more stable than 4.6.5.
Takes 3 days vs. 1 day to crash

Actually that 3 day was an outlier, back to crashing once every 24 hours.

@zwei7 commented on GitHub (Aug 23, 2024): Tried Version 4.6.6 and is more stable than 4.6.5. Takes 3 days vs. 1 day to crash Actually that 3 day was an outlier, back to crashing once every 24 hours.

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@zwei7 commented on GitHub (Aug 31, 2024):

I got the stacktrace of a crash, but the .dump file is 3.69gb and I got 28MB of log files (7 logs). Which do you need cause that dump file is huge. how would you normally want it sent to github for review?

@zwei7 commented on GitHub (Aug 31, 2024): I got the stacktrace of a crash, but the .dump file is 3.69gb and I got 28MB of log files (7 logs). Which do you need cause that dump file is huge. how would you normally want it sent to github for review?

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@luzpaz commented on GitHub (Aug 31, 2024):

@zwei7 Large files can be uploaded too 3rd party download sites i.e. dropbox, google drive, proton drive etc...

@luzpaz commented on GitHub (Aug 31, 2024): @zwei7 Large files can be uploaded too 3rd party download sites i.e. dropbox, google drive, proton drive etc...

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@zwei7 commented on GitHub (Aug 31, 2024):

Ok well here you go, the crash stacktrace, will self destruct after downloaded 50 times and may expire on sept 21
https://filetransfer.io/data-package/gfQtpz0U#link

@zwei7 commented on GitHub (Aug 31, 2024): Ok well here you go, the crash stacktrace, will self destruct after downloaded 50 times and may expire on sept 21 https://filetransfer.io/data-package/gfQtpz0U#link

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Sep 1, 2024):

@zwei7 Thank you, downloaded - haven't looked through them yet.

@xavier2k6 commented on GitHub (Sep 1, 2024): @zwei7 Thank you, downloaded - haven't looked through them yet.

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@Danny3 commented on GitHub (Oct 22, 2024):

On Linux (Debian 12) when running out of space it doesn't crashes.
But it also doesn't stop trying to download that and other files and gives lots of notifications.
I wish that after the first error about running out of space, all downloads will be halted until more space is available instead of showing a lot of notifications and polluting the Execution log!

@Danny3 commented on GitHub (Oct 22, 2024): On Linux (Debian 12) when running out of space it doesn't crashes. But it also doesn't stop trying to download that and other files and gives lots of notifications. I wish that after the first error about running out of space, all downloads will be halted until more space is available instead of showing a lot of notifications and polluting the Execution log!

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@bogorad commented on GitHub (Mar 3, 2025):

Need to have a clear diagnostic: running out of free space, download failed!

@bogorad commented on GitHub (Mar 3, 2025): Need to have a clear diagnostic: **running out of free space, download failed!**

deekerman commented

2026-02-22 02:35:01 -05:00

Author

Owner

@zwei7 commented on GitHub (Mar 3, 2025):

qbittorrent no longer crashes, but I also have ample disk space since I deleted things and I updated to qbittorrent 5.0.4

@zwei7 commented on GitHub (Mar 3, 2025): qbittorrent no longer crashes, but I also have ample disk space since I deleted things and I updated to qbittorrent 5.0.4