starred/qBittorrent

Fork 0

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

v4.0.3.1 doesn't rename file extensions properly #11161

New issue

Closed

opened 2026-02-21 21:11:11 -05:00 by deekerman · 14 comments

deekerman commented

2026-02-21 21:11:11 -05:00

Owner

Originally created by @ericgur on GitHub (Oct 31, 2020).

Please provide the following information

qBittorrent version and Operating System

Windows 10 x64 20H2

If on linux, libtorrent-rasterbar and Qt version

What is the problem

When download completes, some downloaded files (not all) still have the "!qb" file extension.
The files themselves seem complete. Only their name wasn't renamed (remove ".!qb" from end of file name).

What is the expected behavior

Remove ".!qb" from end of file name once download complete.

Steps to reproduce

Download a torrent with more than 1 file in it. The issue occurs in 10/10 torrents I've downloaded.

Extra info(if any)

Reverting to 4.3.0 solved the issue (100%).
Possible hint - if a file within a torrent completes before the others, It will get renamed.
In a torrent with a few small files that get downloaded first, their file name will be correct.
My qBittorrent installation was an upgrade to 4.3.0 which itself was an upgrade to the previous version.

Originally created by @ericgur on GitHub (Oct 31, 2020). **Please provide the following information** ### qBittorrent version and Operating System Windows 10 x64 20H2 ### If on linux, libtorrent-rasterbar and Qt version -- ### What is the problem When download completes, some downloaded files (not all) still have the "!qb" file extension. The files themselves seem complete. Only their name wasn't renamed (remove ".!qb" from end of file name). ### What is the expected behavior Remove ".!qb" from end of file name once download complete. ### Steps to reproduce Download a torrent with more than 1 file in it. The issue occurs in 10/10 torrents I've downloaded. ### Extra info(if any) Reverting to 4.3.0 solved the issue (100%). Possible hint - if a file within a torrent completes before the others, It will get renamed. In a torrent with a few small files that get downloaded first, their file name will be correct. My qBittorrent installation was an upgrade to 4.3.0 which itself was an upgrade to the previous version.

deekerman

2026-02-21 21:11:11 -05:00

closed this issue
added the
Core

Can't reproduce
labels

deekerman commented

2026-02-21 21:11:15 -05:00

Author

Owner

@glassez commented on GitHub (Nov 6, 2020):

@thalieht, @xavier2k6, can you test and confirm it?

@glassez commented on GitHub (Nov 6, 2020): @thalieht, @xavier2k6, can you test and confirm it?

deekerman commented

2026-02-21 21:11:15 -05:00

Author

Owner

@thalieht commented on GitHub (Nov 6, 2020):

Can't reproduce in 4.3.0 nor 4.3.0.1

@thalieht commented on GitHub (Nov 6, 2020): Can't reproduce in 4.3.0 nor 4.3.0.1

deekerman commented

2026-02-21 21:11:15 -05:00

Author

Owner

@thalieht commented on GitHub (Nov 6, 2020):

Maybe some antivirus or whatever is locking the files and doesn't let qBt rename them.

@thalieht commented on GitHub (Nov 6, 2020): Maybe some antivirus or whatever is locking the files and doesn't let qBt rename them.

deekerman commented

2026-02-21 21:11:15 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Nov 6, 2020):

I currently download with the .!qb extension enabled & not an issue for me - also on windows 10 x64 20H2 Build:19042.610

I only have windows defender, however my File pool size is not the default of 40 it is set to 8000

EDIT: Official qBittorrent 4.3.0.1

@xavier2k6 commented on GitHub (Nov 6, 2020): I currently download with the `.!qb` extension enabled & not an issue for me - also on windows 10 x64 20H2 Build:19042.610 I only have `windows defender`, however my `File pool size` is not the default of `40` it is set to `8000` EDIT: Official qBittorrent 4.3.0.1

deekerman commented

2026-02-21 21:11:15 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Nov 6, 2020):

@ericgur could you provide a link to an example torrent if possible?

@xavier2k6 commented on GitHub (Nov 6, 2020): @ericgur could you provide a link to an example torrent if possible?

deekerman commented

2026-02-21 21:11:15 -05:00

Author

Owner

@ericgur commented on GitHub (Nov 6, 2020):

Practically any torrent from showrss does the trick.
Example:

The Mandalorian S02E02 1080p DSNP WEBRip DDP5 1 Atmos x264 PHOENiX.zip
The large file will get the issue. Seems like only the file(s) that get completed when the torrent completes has the issue.
I'm back to v4.0.3 and see zero issues.
I'll try to increase the file pool size to 8000 with v4.0.3.1 and report back.

For AV, I use AVG Free.

@ericgur commented on GitHub (Nov 6, 2020): Practically any torrent from showrss does the trick. Example: [The Mandalorian S02E02 1080p DSNP WEBRip DDP5 1 Atmos x264 PHOENiX.zip](https://github.com/qbittorrent/qBittorrent/files/5501334/The.Mandalorian.S02E02.1080p.DSNP.WEBRip.DDP5.1.Atmos.x264.PHOENiX.zip) The large file will get the issue. Seems like only the file(s) that get completed when the torrent completes has the issue. I'm back to v4.0.3 and see zero issues. I'll try to increase the file pool size to 8000 with v4.0.3.1 and report back. For AV, I use AVG Free.

deekerman commented

2026-02-21 21:11:16 -05:00

Author

Owner

@ericgur commented on GitHub (Nov 6, 2020):

Initial results using 4.0.3.1 with higher file pool size (8000) are good.
If the default of 40 is too low, maybe it should increase.
It's a little strange that 4.0.3 and earlier versions (on earlier OS versions) don't have this issue but 4.3.0.1 does.

@ericgur commented on GitHub (Nov 6, 2020): Initial results using 4.0.3.1 with higher file pool size (8000) are **good**. If the default of 40 is too low, maybe it should increase. It's a little strange that 4.0.3 and earlier versions (on earlier OS versions) don't have this issue but 4.3.0.1 does.

deekerman commented

2026-02-21 21:11:16 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Nov 6, 2020):

8000 may be a bit drastic for the typical user....if it is to be raised....needs to be more realistic perhaps......

Could you try setting it to 100?

If you still experience the issue, could you increment it by say 10 until you no longer experience the issue.

If set at 100 & you don't experience the issue, could you decrease it by say 10 until you experience the issue again.

@xavier2k6 commented on GitHub (Nov 6, 2020): `8000` may be a bit drastic for the typical user....if it is to be raised....needs to be more realistic perhaps...... Could you try setting it to `100`? If you still experience the issue, could you increment it by say `10` until you no longer experience the issue. If set at `100` & you don't experience the issue, could you decrease it by say `10` until you experience the issue again.

deekerman commented

2026-02-21 21:11:16 -05:00

Author

Owner

@ericgur commented on GitHub (Nov 7, 2020):

100 also works (so far).
I'll try lower settings in the following days.

@ericgur commented on GitHub (Nov 7, 2020): 100 also works (so far). I'll try lower settings in the following days.

deekerman commented

2026-02-21 21:11:16 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (Nov 7, 2020):

@xavier2k6

You're not isolating the anti-virus variable. @ericgur is using AVG while you are using Windows Defender. It would be interesting for you to test with the file pool set to 40. If there is no problem, we can safely claim this is AVG's fault. Of course, raising the default is likely the best way forward still, since AFAIK there is no virtually no downside to raising it (within reason). Not having problems with some antivruses by default is better than having problems with some antiviruses by default.

@FranciscoPombal commented on GitHub (Nov 7, 2020): @xavier2k6 You're not isolating the anti-virus variable. @ericgur is using AVG while you are using Windows Defender. It would be interesting for you to test with the file pool set to `40`. If there is no problem, we can safely claim this is AVG's fault. Of course, raising the default is likely the best way forward still, since AFAIK there is no virtually no downside to raising it (within reason). Not having problems with some antivruses by default is better than having problems with some antiviruses by default.

deekerman commented

2026-02-21 21:11:16 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Nov 8, 2020):

You're not isolating the anti-virus variable.

I'm isolating one variable (which in my opinion is more common) - because I see two main use cases/anti-virus variables:

Most users generally won't have excluded qBittorrent/download folder from scans.

Hence why I believe raising file pool size would be of benefit in this situation.

Users who do exclude qBittorrent/download folder from scans.

Wouldn't experience this issue.

I will change my file pool size back to default 40 for testing purposes.....

One thing to note though, If the default file pool size is to be raised what needs to be taken in to account as well is that AVG may be ok with say 50 but McAfee may need 60 & let's say BitDefender needs 80.

Do we raise it to a One size fits all?
Do we raise it case by case (which wouldn't be really productive)
What effect would raising file pool size on the closing of qBittorrent?

@xavier2k6 commented on GitHub (Nov 8, 2020): >You're not isolating the anti-virus variable. I'm isolating one variable (which in my opinion is more common) - because I see two main use cases/anti-virus variables: 1. Most users generally won't have excluded qBittorrent/download folder from scans. Hence why I believe raising `file pool size` would be of benefit in this situation. 2. Users who **do** exclude qBittorrent/download folder from scans. Wouldn't experience this issue. I will change my `file pool size` back to default `40` for testing purposes..... One thing to note though, **If** the default `file pool size` is to be raised what needs to be taken in to account as well is that `AVG` may be ok with say `50` but `McAfee` may need `60` & let's say `BitDefender` needs `80`. 1. Do we raise it to a One size fits all? 2. Do we raise it case by case (which wouldn't be really productive) 3. What effect would raising `file pool size` on the closing of qBittorrent?

deekerman commented

2026-02-21 21:11:16 -05:00

Author

Owner

@glassez commented on GitHub (Nov 8, 2020):

Guys, can you explain to me how file pool size and antivirus software play here? IIRC, antivirus can lock some files after downloading. But how file pool size affects it?
Sorry I have no time to dig into it myself.

@glassez commented on GitHub (Nov 8, 2020): Guys, can you explain to me how `file pool size` and antivirus software play here? IIRC, antivirus can lock some files after downloading. But how `file pool size` affects it? Sorry I have no time to dig into it myself.

deekerman commented

2026-02-21 21:11:16 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Nov 8, 2020):

@glassez

sets the upper limit on the total number of files this session will keep open. The reason why files are left open at all is that some anti virus software hooks on every file close, and scans the file for viruses. deferring the closing of the files will be the difference between a usable system and a completely hogged down system. Most operating systems also has a limit on the total number of file descriptors a process may have open.

ref: https://www.libtorrent.org/reference-Settings.html#file_pool_size

@xavier2k6 commented on GitHub (Nov 8, 2020): @glassez >sets the upper limit on the total number of files this session will keep open. The reason why files are left open at all is that some anti virus software hooks on every file close, and scans the file for viruses. deferring the closing of the files will be the difference between a usable system and a completely hogged down system. Most operating systems also has a limit on the total number of file descriptors a process may have open. ref: https://www.libtorrent.org/reference-Settings.html#file_pool_size

deekerman commented

2026-02-21 21:11:16 -05:00

Author

Owner

@ericgur commented on GitHub (Nov 8, 2020):

I have tried various file pool size settings, including going to 40 and the issue is gone.
Since the issue happened on ~10 different torrents, spanning several days this looked a simple issue.
This may be related to how the default value is consumed by the app.
Since I can't reproduce anymore, I'm closing the ticket.

Thanks for the excellent support!

@ericgur commented on GitHub (Nov 8, 2020): I have tried various file pool size settings, including going to 40 and the issue is gone. Since the issue happened on ~10 different torrents, spanning several days this looked a simple issue. This _may_ be related to how the default value is consumed by the app. Since I can't reproduce anymore, I'm closing the ticket. Thanks for the excellent support!