qBittorrent freezes on completed downloads #7609

Closed
opened 2026-02-21 19:04:15 -05:00 by deekerman · 14 comments
Owner

Originally created by @amno1 on GitHub (Aug 14, 2018).

Please provide the following information

qBittorrent version and Operating System

qbittorrent-git 4.1.1.r141.g5f8feec1c-1

Linux pascal 4.18.0-arch1-1-ARCH #1 SMP PREEMPT Mon Aug 13 11:52:58 UTC 2018 x86_64 GNU/Linux

If on linux, libtorrent and Qt version

libtorrent 0.13.7-1
Qt5

What is the problem

Application freezes until a torrent file is written to disk (seems like). Nothing is responding until all disk access is done. If there are several downloads that finish at the same time then application remains frozen until all files are written. There is no gui responsiveness att all during that time.

What is the expected behavior

Gui should not be frozen while a file is written or checked after finished download.

Steps to reproduce

Download a file.

Extra info(if any)

Same behaviour does not happen on Windows OS.

Originally created by @amno1 on GitHub (Aug 14, 2018). **Please provide the following information** ### qBittorrent version and Operating System qbittorrent-git 4.1.1.r141.g5f8feec1c-1 Linux pascal 4.18.0-arch1-1-ARCH #1 SMP PREEMPT Mon Aug 13 11:52:58 UTC 2018 x86_64 GNU/Linux ### If on linux, libtorrent and Qt version libtorrent 0.13.7-1 Qt5 ### What is the problem Application freezes until a torrent file is written to disk (seems like). Nothing is responding until all disk access is done. If there are several downloads that finish at the same time then application remains frozen until all files are written. There is no gui responsiveness att all during that time. ### What is the expected behavior Gui should not be frozen while a file is written or checked after finished download. ### Steps to reproduce Download a file. ### Extra info(if any) Same behaviour does not happen on Windows OS.
deekerman 2026-02-21 19:04:15 -05:00
Author
Owner

@thalieht commented on GitHub (Aug 14, 2018):

qBt uses Libtorrent rasterbar, you said version for libtorrent rakshasa

@thalieht commented on GitHub (Aug 14, 2018): qBt uses Libtorrent rasterbar, you said version for libtorrent rakshasa
Author
Owner

@amno1 commented on GitHub (Aug 14, 2018):

This problem has been happening during a period of over a year or so, since I start using qBittorrent on my Linux box. I was just lazy to rapport it before. So this has happened over different libtorrent, qt and qbittorrent versions. Check how you lock your files during writes, checks etc. It might be some threading problem.

@amno1 commented on GitHub (Aug 14, 2018): This problem has been happening during a period of over a year or so, since I start using qBittorrent on my Linux box. I was just lazy to rapport it before. So this has happened over different libtorrent, qt and qbittorrent versions. Check how you lock your files during writes, checks etc. It might be some threading problem.
Author
Owner

@FranciscoPombal commented on GitHub (Aug 14, 2018):

@amno1, your problem is not the libtorrent version per se, but rather that you are using the wrong libtorrent.

There are 2 libtorrents, libtorrent-rasterbar and libtorrent-rakshasa.
Both are pretty different, and recent versions use very different version number schemes. The version number that you posted is consistent with libtorrent-rakshasa, not rasterbar. Qbittorrent will not work correctly with libttorrent-rakshasa. Please install the correct package and report back.

@FranciscoPombal commented on GitHub (Aug 14, 2018): @amno1, your problem is not the libtorrent version per se, but rather that you are using the wrong libtorrent. There are 2 libtorrents, libtorrent-rasterbar and libtorrent-rakshasa. Both are pretty different, and recent versions use very different version number schemes. The version number that you posted is consistent with libtorrent-rakshasa, not rasterbar. Qbittorrent will not work correctly with libttorrent-rakshasa. Please install the correct package and report back.
Author
Owner

@kevin-stuart commented on GitHub (Aug 19, 2018):

I had the same problem with 4.1.1 from the stable PPA on bionic. I just installed 4.1.2 and checked again, the problem persists there. So the versions now for me are:

qbittorrent: 4.1.2.99~201808180832-6495-03375a7~ubuntu18.04.1
libtorrent-rasterbar9: 1.1.9+git20180812.0bcf6cef23+patched-configure-1ppa1~bionic1

I'm not sure if it started with 4.1.1 and if this problem was not present on 4.1.0, but I think it started on some version after bionic. I also have another install of bionic with the same versions that does not have the problem, but I cannot figure out the cause or what is different.

This is really annoying with a lot of small torrents, it will make the interface or webui totally unresponsive. I don't know why the freeze occurs, eveb with very small files (1-3 MB) the length is always the same. I also have the completion directory on the same partition so the move for completion should instant. But each finishing torrent freezes for around 10 seconds.

@kevin-stuart commented on GitHub (Aug 19, 2018): I had the same problem with 4.1.1 from the stable PPA on bionic. I just installed 4.1.2 and checked again, the problem persists there. So the versions now for me are: ``` qbittorrent: 4.1.2.99~201808180832-6495-03375a7~ubuntu18.04.1 libtorrent-rasterbar9: 1.1.9+git20180812.0bcf6cef23+patched-configure-1ppa1~bionic1 ``` I'm not sure if it started with 4.1.1 and if this problem was not present on 4.1.0, but I think it started on some version after bionic. I also have another install of bionic with the same versions that does not have the problem, but I cannot figure out the cause or what is different. This is really annoying with a lot of small torrents, it will make the interface or webui totally unresponsive. I don't know why the freeze occurs, eveb with very small files (1-3 MB) the length is always the same. I also have the completion directory on the same partition so the move for completion should instant. But each finishing torrent freezes for around 10 seconds.
Author
Owner

@amno1 commented on GitHub (Aug 21, 2018):

Indeed I have found I had two libtorrent libraries installed.
± |master ✓| → pacman -Q | grep torrent
libtorrent 0.13.7-1
libtorrent-rasterbar 1:1.1.9-1
qbittorrent-git 4.1.1.r141.g5f8feec1c-1

I have uninstalled libtorrent 0.13.7-1. However I am not sure if that solved the problem, will have to see when I download something :-)

@amno1 commented on GitHub (Aug 21, 2018): Indeed I have found I had two libtorrent libraries installed. ± |master ✓| → pacman -Q | grep torrent libtorrent 0.13.7-1 libtorrent-rasterbar 1:1.1.9-1 qbittorrent-git 4.1.1.r141.g5f8feec1c-1 I have uninstalled libtorrent 0.13.7-1. However I am not sure if that solved the problem, will have to see when I download something :-)
Author
Owner

@amno1 commented on GitHub (Aug 21, 2018):

Njah, tested and it definitely still freezes despite having correct libtorrent installed. I have uninstalled libtorrent-0.13.7-1 and am running with libtorrent-rasterbar 1:1.1.9-1. Same freezes still occur so it wasn't the wrong library.

@amno1 commented on GitHub (Aug 21, 2018): Njah, tested and it definitely still freezes despite having correct libtorrent installed. I have uninstalled libtorrent-0.13.7-1 and am running with libtorrent-rasterbar 1:1.1.9-1. Same freezes still occur so it wasn't the wrong library.
Author
Owner

@kevin-stuart commented on GitHub (Aug 26, 2018):

There is no perceptible load on CPU or disk, so it really is unclear why qBittorrent is stalled. The stall seems to be the same for large or small files.

I mainly use the webui, which is also stalled, so it seems that there is some operation going on that stalls all threads (or at least the main thread that is also linked to the webui), not just the GUI thread. Since the regular GUI should be updating a bit faster, I sometimes see the state "moving" as last state before the stall instead of "seeding", so maybe the problematic code is in moving. For me, moving should just be a rename to a different directory.

It's a bit of a shame that the intial reported bug did not gain more attention when it was opened, I think the maintainers thought that the bug was due to a wrong library version. And now the visibility of this reported bug is low because it is old.

@kevin-stuart commented on GitHub (Aug 26, 2018): There is no perceptible load on CPU or disk, so it really is unclear why qBittorrent is stalled. The stall seems to be the same for large or small files. I mainly use the webui, which is also stalled, so it seems that there is some operation going on that stalls all threads (or at least the main thread that is also linked to the webui), not just the GUI thread. Since the regular GUI should be updating a bit faster, I sometimes see the state "moving" as last state before the stall instead of "seeding", so maybe the problematic code is in moving. For me, moving should just be a rename to a different directory. It's a bit of a shame that the intial reported bug did not gain more attention when it was opened, I think the maintainers thought that the bug was due to a wrong library version. And now the visibility of this reported bug is low because it is old.
Author
Owner

@amno1 commented on GitHub (Aug 31, 2018):

Before I opened this issue, I was looking through the code for Qt client to see where threads could be blocking, but I wasn't able to find it myself. But I am not acquainted with the qbittorrents code.

@amno1 commented on GitHub (Aug 31, 2018): Before I opened this issue, I was looking through the code for Qt client to see where threads could be blocking, but I wasn't able to find it myself. But I am not acquainted with the qbittorrents code.
Author
Owner

@kevin-stuart commented on GitHub (Sep 2, 2018):

Just out of curiousity: What filesystem are you using?

Edit: Do you still have the problem if you disable all notifications in Preferences/Advanced?

@kevin-stuart commented on GitHub (Sep 2, 2018): Just out of curiousity: What filesystem are you using? Edit: Do you still have the problem if you disable all notifications in Preferences/Advanced?
Author
Owner
@amno1 commented on GitHub (Sep 2, 2018): Ext4. Skickat från min Samsung Galaxy-smartphone. -------- Originalmeddelande -------- Från: kevin-stuart <notifications@github.com> Datum: 2018-09-02 14:04 (GMT+01:00) Till: qbittorrent/qBittorrent <qBittorrent@noreply.github.com> Kopia: amno1 <arthur.miller@live.com>, Mention <mention@noreply.github.com> Rubrik: Re: [qbittorrent/qBittorrent] qBittorrent freezes on completed downloads (#9328) Just out of curiousity: What filesystem are you using? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fqbittorrent%2FqBittorrent%2Fissues%2F9328%23issuecomment-417926038&data=02%7C01%7C%7Cbe8a5ee2b1b24b0a04bc08d610cc3bee%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636714866690705300&sdata=sepSgqrD2yB6EyZM%2FGwfSwWbH50LqzR6Af81s9adu18%3D&reserved=0>, or mute the thread<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAG1fx_bWiDqlmsvnV7vorXPgTlE_JCEDks5uW8lKgaJpZM4V7z17&data=02%7C01%7C%7Cbe8a5ee2b1b24b0a04bc08d610cc3bee%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636714866690705300&sdata=UXtlpSxM515YJS3I%2FnJ1wzllktyej89xh456XrPSLU4%3D&reserved=0>.
Author
Owner

@kevin-stuart commented on GitHub (Sep 3, 2018):

I guess you did not see my edit via email. Since I had another computer that did not have the problem, I tried comparing and at first thought that the filesystem was a factor. It turned out to be wrong. But I discovered that I think disabling notifications completely fixes the problem for me.

@kevin-stuart commented on GitHub (Sep 3, 2018): I guess you did not see my edit via email. Since I had another computer that did not have the problem, I tried comparing and at first thought that the filesystem was a factor. It turned out to be wrong. But I discovered that I think disabling notifications completely fixes the problem for me.
Author
Owner

@amno1 commented on GitHub (Sep 3, 2018):

Thanks, I just tried to disable notifications too, it seems to solve the issue. I only tested one torrent. Will test more later in the week.

Yeah, you are right, I missed your edits.

@amno1 commented on GitHub (Sep 3, 2018): Thanks, I just tried to disable notifications too, it seems to solve the issue. I only tested one torrent. Will test more later in the week. Yeah, you are right, I missed your edits.
Author
Owner

@amno1 commented on GitHub (Sep 4, 2018):

I think disabling notifications solved the issue for me. I have just downloaded few small torrents file for test and I can't see any locking.

@amno1 commented on GitHub (Sep 4, 2018): I think disabling notifications solved the issue for me. I have just downloaded few small torrents file for test and I can't see any locking.
Author
Owner

@sledgehammer999 commented on GitHub (Oct 29, 2020):

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.

@sledgehammer999 commented on GitHub (Oct 29, 2020): This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable. If you experience the reported problem or similar in the **latest** version, please open a new issue report with the requested information in the issue template. A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression. Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar. Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression. Thank you for your contributions.
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#7609
No description provided.