bug: spamming recursive label copy #2798

Closed
opened 2026-02-21 16:24:56 -05:00 by deekerman · 4 comments
Owner

Originally created by @snoukkis on GitHub (Jul 16, 2015).

I ended up with really many recursive copies of a torrent and others which I relabeled together.

Steps:

  1. Check the "Append the label of the torrent to the save path" option.
  2. Start downloading any torrent that creates a directory, e.g. "foldername".
  3. Not sure if this step is necessary: wait until torrent completes.
  4. relabel that torrent (and maybe bunch of others like I did?) to "foldername", i.e. exactly same as the folder created by torrent before
  5. qbittorrent should try to move the torrents to this folder

Expected result:
Torrent download folder should contain: foldername\foldername...;foldername\otherrelabeledtorrent...;etc.

Actual result:
Torrent download folder contains an endless list of foldername\foldername\foldername\foldername\foldername\foldername\etc. , each containing all the files of each relableled torrent. To be fair the recursion did seem to stop at some point and didn't crash anything either. It did hang for a moment though when I tried to open the location from "Content" panel.

Environment:

  • Windows 7 x64
  • qBittorrent 3.2.1
Originally created by @snoukkis on GitHub (Jul 16, 2015). I ended up with really many recursive copies of a torrent and others which I relabeled together. Steps: 1. Check the "Append the label of the torrent to the save path" option. 2. Start downloading any torrent that creates a directory, e.g. "foldername". 3. Not sure if this step is necessary: wait until torrent completes. 4. relabel that torrent (and maybe bunch of others like I did?) to "foldername", i.e. exactly same as the folder created by torrent before 5. qbittorrent should try to move the torrents to this folder Expected result: Torrent download folder should contain: foldername\foldername\...;foldername\otherrelabeledtorrent\...;etc. Actual result: Torrent download folder contains an endless list of foldername\foldername\foldername\foldername\foldername\foldername\etc. , each containing all the files of each relableled torrent. To be fair the recursion did seem to stop at some point and didn't crash anything either. It did hang for a moment though when I tried to open the location from "Content" panel. Environment: - Windows 7 x64 - qBittorrent 3.2.1
Author
Owner

@ngosang commented on GitHub (Jul 19, 2015):

I tested v3.3.0 alpha and this problem is fixed. If this problem is annoying you try downloading 3.3.0 https://qbforums.shiki.hu/index.php/topic,3606.0.html

@ngosang commented on GitHub (Jul 19, 2015): I tested v3.3.0 alpha and this problem is fixed. If this problem is annoying you try downloading 3.3.0 https://qbforums.shiki.hu/index.php/topic,3606.0.html
Author
Owner

@sledgehammer999 commented on GitHub (Jul 19, 2015):

Yes, try 3.3.0. It haves major changes in handling paths. However those changes cannot be backported to the v3.2.x series.

@sledgehammer999 commented on GitHub (Jul 19, 2015): Yes, try 3.3.0. It haves major changes in handling paths. However those changes cannot be backported to the v3.2.x series.
Author
Owner

@snoukkis commented on GitHub (Jul 19, 2015):

Good to hear path handling is improved in future releases. Does that change have an issue?

Offtopic: does the changed path handling fix problems with multiple torrents downloading into same subdirectory/files?

@snoukkis commented on GitHub (Jul 19, 2015): Good to hear path handling is improved in future releases. Does that change have an issue? Offtopic: does the changed path handling fix problems with multiple torrents downloading into same subdirectory/files?
Author
Owner

@sledgehammer999 commented on GitHub (Jul 19, 2015):

If you download into the same file it can never be fixed. You should ask libtorrent-rasterbar to handle that issue.
The change doesn't have an issue, they are part of a major code refactoring and shouldn't be backported to the stable branch. (although 3.3.0 is very stable anyways)

@sledgehammer999 commented on GitHub (Jul 19, 2015): If you download into the same **file** it can never be fixed. You should ask libtorrent-rasterbar to handle that issue. The change doesn't have an issue, they are part of a major code refactoring and shouldn't be backported to the stable branch. (although 3.3.0 is very stable anyways)
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#2798
No description provided.