torrents get lost

[Xuefer]

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.

[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.

[Xuefer]

Replying to 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 too

[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?

alert queue size is set to 100 in ltconfig "minimum memory usage" prest, which will sure trigger this bug