mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
WebUI freeze in Safari on iOS/iPadOS when typing save path with many subfolders (regression introduced in v5.1.x, path-autocomplete) #17311
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#17311
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @menkromsen on GitHub (Nov 17, 2025).
qBittorrent & operating system versions
qBittorrent version: 5.1.3
Tested both the official Windows x64 5.1.3 version -and the Linuxserver image version 5.1.2.
Client devices: iPhone 14 Plus, iPad Pro 11"
Client OS: iOS/iPadOS 18.6.2
Browser: Safari
Qt version: 6.8.x (from Linuxserver image)
libtorrent-rasterbar: 2.0.x (from Linuxserver image)
What is the problem?
The WebUI freezes in Safari on iOS/iPadOS when typing a save path that contains a large number of subdirectories. (tested 887 folders)
Regression introduced in qBittorrent 5.1.0 with the new path autocomplete (PR #20906).
Still occurs in 5.1.3.
Because of this issue I'm currently using version 5.0.4 without the path-autocomplete function.
Steps to reproduce
Run qBittorrent using version 5.1.3
Open the WebUI in Safari on iPhone or an iPad.
Add a torrent.
Type a path that contains many subfolders, e.g. /movies/ (~1000 subdirectories).
Safari becomes unresponsive after a few seconds and must be force-closed.
Additional context
Expected behavior
Typing a save path should not cause the browser to freeze, even if the folder contains many subdirectories.
Actual behavior
Safari freezes completely after a short delay (not instantly).
Entire browser becomes unresponsive. Most force-close the browser and open again to regain control.
Reproducible on multiple devices:
iPhone 14 Plus – iOS 18.6.2
iPad Pro 11" – iPadOS 18.6.2
-No ad blockers installed.
Regression
Affected: 5.1.0 – 5.1.3
Not affected: 5.0.4 (no path-autocomplete feature)
Suggested improvements
Add a toggle in WebUI settings to disable path autocomplete. I don't need this function - and the UI becomes cluttered with the auto-suggestions appearing.
Limit autocomplete result count (e.g., max 50–100).
Lazy-load folder suggestions instead of rendering thousands at once.
Log(s) & preferences file(s)
No logs needed I guess, it is Safari that is freezing.
@glassez commented on GitHub (Nov 17, 2025):
@qbittorrent/web-developers, @pktiuk
@menkromsen commented on GitHub (Dec 2, 2025):
No love for this bug yet it seems.
I'm no code-guru in any way, but asked ChatGPT about the changes pktiuk made in PR https://github.com/qbittorrent/qBittorrent/pull/20906 -and had ChatGPT give some suggestions on how to fix it. It's fair to say that ChatGPT was not impressed by this logic and meltdown of the mobile browser is bound to happen if there are lots of underfolders available.
I may try to contribute myself if not anybody else feels the call. I think there should be implemented some changes so that this feature could be toggled off in the settings. That is important.
And then, the logic needs to be improved so that the feature actually works as intended without crashing the browser.
@pktiuk commented on GitHub (Dec 7, 2025):
I guess that you can try to write a patch and start using it with your setup.
And if it works, then you could upload it as a PR.