Deluge Forum

Hi,

I've been trying to switch over from kTorrent to Deluge. I have Deluge 1.3.1-1 and libtorrent 0.14.10.0 running in aptosid Linux with the 2.6.36 kernel on an AMD 4850e processor with 2GB RAM.

With a fresh install of Deluge and empty /.config/Deluge directory, File/Quit worked OK, and I was quitting without any problem after adding every 100 or so torrents. When I got up to 498 torrents, File/Quit froze the application. This happened last night, too, after I had added over 1000 torrents in one session, so I started over with a fresh install to see when exactly it would start happening. Quit from the tray freezes, too. In either case, Deluge continues to appear as a process in htop, but using 0% CPU.

I also notice that when I force quit and restart the application, a large number of torrents go into "Checking" mode, but they're not checking, they're just sitting there.

I have about 3000 torrents I hope to seed. Deluge looks very good so far as a kTorrent replacement, with this exception.

I guess I'd ordinarily report this as a bug, but since the File/Quit hang bug is listed as "fixed" in this release, I thought I'd try here first.

Thanks!

Do you have any plugins enabled?

So was 498 the minimum amount of torrents needed to trigger the bug?

Sorry, forgot to mention, no plugins enabled. I was adding about 100 torrents at a time and quitting after each round to test File/Quit, and 400 or so torrents worked OK, but 500 or so didn't.

I've been testing some things, and will try to boil it down to a fairly concise description.

First I noticed that removing torrents from the /deluge/state folder to get to a smaller number doesn't make File/Quit start working again, but removing or renaming the torrents.state file does.

I can gradually add torrents until I get up into the mid- to high-400s, and then eventually File/Quit hangs. I can't pin it down to an exact number, i.e. there isn't one, sometimes it's in the 460s and sometimes it's in the 480s, but eventually if I add enough torrents (just in pause mode without checking or seeding), File/Quit hangs.

By the way, are you running deluge in classic mode or as a separate client and daemon?
If it's the latter, is the daemon local or remote?

Hi, Johnny,

I'm running in classic mode. Thanks!

Today I noticed that if I leave Deluge running for, say, 5 minutes after it starts with a larger number of torrents (even 600+), it will quit. I can't see what it's busy doing that it needs to finish before it will allow me to quit. If I try to quit before that, though, the quit won't happen even if I wait.

All 600+ torrents are paused, so there's no attempting to connect going on.