mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Can't add a torrent file: "metadata too large" #4611
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#4611
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 @FlatApio on GitHub (Aug 11, 2016).
Hello
I have an issue with adding a torrent file to download list. Error message reads "metadata too large".
I have seen similar issue being already posted here and even marked as solved, however it seems that it's still causing a problems with certain torrent files.
qBittorrent: v3.3.6
Qt: 5.7.0
libtorrent: 1.0.9.0
boost: 1.61.0
OS version: Windows 7 Pro x64
File I'm trying to add:
https://dl.dropbox.com/u/73920008/MMD.torrent
Thanks in advance for any support you could provide.
@Gliscor commented on GitHub (Sep 3, 2016):
I can reproduce this bug on Linux 32 bits, qBittorrent 3.3.6. Qt:4.8.6 libtorrent: 1.0.7.0 Boost: 1.54.0
@ngosang commented on GitHub (Sep 16, 2018):
We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.