qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
26.94k stars 3.88k forks source link

Client freezes when trying to open a network folder #18589

Open stalkerok opened 1 year ago

stalkerok commented 1 year ago

qBittorrent & operating system versions

2023-02-18_125917

What is the problem?

Client freezes when trying to open a network folder

Steps to reproduce

  1. Start downloading to a local network folder
  2. Click open destination folder
  3. Client freezes

Additional context

No response

Log(s) & preferences file(s)

No response

glassez commented 1 year ago
  1. Start downloading to a local network folder

What do you mean by "local network folder"?

stalkerok commented 1 year ago

Downloading takes place on another PC connected via local network. Two screenshots, the first before clicking "open destination folder", the second after. 2023-02-18_133347 2023-02-18_133432

stalkerok commented 1 year ago

qBittorrent.zip run client as admin

If you don't try to kill the process, it will eventually open the folder.

glassez commented 1 year ago

Downloading takes place on another PC connected via local network.

Could it be due to a lack of bandwidth, which is occupied by the data transfer of the torrent itself?

stalkerok commented 1 year ago

I think I understood what's going on. This state is caused by the Preallocation=true option, until the client sends the entire volume, "open destination folder" causes a hang, and only after completion the interface becomes responsive.

xavier2k6 commented 8 months ago

@stalkerok Is this still an issue with qBittorrent 4.6.2/master??

stalkerok commented 8 months ago

No way to test it, maybe later.

stalkerok commented 8 months ago

https://github.com/qbittorrent/qBittorrent/assets/63958081/769f61cc-23bc-4163-84cd-0a2da813ed12

5.0 behavior is similar.

luzpaz commented 4 weeks ago

@stalkerok can you still reproduce on 4.6.5 ?

stalkerok commented 4 weeks ago

@luzpaz check out the video, it uses 4.6.2, and as I wrote before

5.0 behavior is similar.

I don't think anything has changed.