Skip to content

[Core] Work around libtorrent size limit #483

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

marcan
Copy link

@marcan marcan commented May 29, 2025

When loading a torrent_info by file path, libtorrent has a hardcoded size limit that some torrents exceed. This means that the torrent can be added normally to deluge, but on restart it fails to load the file from the state directory and the torrent is lost.

Work around the hardcoded buffer size limit by reading in the file directly and passing the buffer.

See: https://libtorrent-discuss.narkive.com/wYACQDb7/libtorrent-loading-a-big-torrent-fails
Fixes: https://forum.deluge-torrent.org/viewtopic.php?t=56856

When loading a torrent_info by file path, libtorrent has a hardcoded
size limit that some torrents exceed. This means that the torrent can be
added normally to deluge, but on restart it fails to load the file from
the state directory and the torrent is lost.

Work around the hardcoded buffer size limit by reading in the file
directly and passing the buffer.

See: https://libtorrent-discuss.narkive.com/wYACQDb7/libtorrent-loading-a-big-torrent-fails
Fixes: https://forum.deluge-torrent.org/viewtopic.php?t=56856
@marcan marcan force-pushed the raise_torrent_size_limit branch from ffd3e7d to 3f5d482 Compare May 29, 2025 06:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant