[Deluge] #3571: torrents get lost
Deluge
----------------------------+------------------------
Reporter: Xuefer | Type: bug
Status: new | Priority: critical
Milestone: needs verified | Component: libtorrent
Version: 2.1.0 | Keywords:
----------------------------+------------------------
steps to reproduce:
1. make sure there're more than 128 torrents added, in any state
2. use ltconfig plugin to set alert_queue_size to 100 (or load preset:
minimal memory usage, which use 100 for alert_queue_size)
3. restart deluge
only about 126~130 torrents get loaded. restart deluge again you'll see
size of torrents.state get slim down to a few kbytes from mbytes
"Finished loading 427 torrents in 0:00:06.760026" is not appearing in the
log. unless the count is slim down
alert_queue_size = 100 is not required for this to happen
Reason: loading existing torrents, rely on alert_queue as callback
Suggestion: need a reliable callback mechanic other than alert_queue which
is limited by size.
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3571>
Deluge <https://deluge-torrent.org/>
Deluge Project
Deluge
-------------------------+----------------------------
Reporter: Xuefer | Owner:
Type: bug | Status: new
Priority: critical | Milestone: needs verified
Component: libtorrent | Version: 2.1.0
-------------------------+----------------------------
Comment (by Cas):
Yes Deluge has a queue size default of 10000 since the queue is critical
to functionality so not unexpected that a very low value would cause
issues
> Alerts is the main mechanism for libtorrent to report errors and events.
Deluge requires the queue for events but there are potential improvements
to alert handling.
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3571#comment:1>
Deluge
-------------------------+----------------------------
Type: bug | Status: new
Priority: critical | Milestone: needs verified
Component: libtorrent | Version: 2.1.0
-------------------------+----------------------------
Comment (by Xuefer):
Replying to [comment:1 Calum]:
> Yes Deluge has a queue size default of 10000 since the queue is critical
to functionality so not unexpected that a very low value would cause
issues
>
> > Alerts is the main mechanism for libtorrent to report errors and
events.
>
> Deluge requires the queue for events but there are potential
improvements to alert handling.
Can someone take a look at this? Critical events shouldn't be drop for any
reason, otherwise bad things happens. "a very low value" is not required
to reproduce the bug, a slow PC can reproduce the bug on a busy deluge
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/3571#comment:2>
Deluge
-------------------------+----------------------------
Reporter: Xuefer | Owner: (none)
Priority: critical | Milestone: needs verified
Component: libtorrent | Version: 2.1.0
-------------------------+----------------------------
Comment (by Xuefer):
an idea would be to set large enough (larger than normal) alert queue size
and mask other alerts allowing only needed for loading/saving torrent list
when and only when loading/saving torrent list. can anyone implement this?
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/3571#comment:3>