0.5.8.3 locks up occasionally

[jarlath]

Whenever I restore from the task bar or from the system tray, Deluge freezes up for up to a minute or two.

Then it's usable again but as soon as I give another window focus, I'm have to go through another freeze before I can use it.

I'm running Ubuntu Gutsy 7.04 on a Core 2 Duo with 2Gigs of ram.

Thanks for making this software available for linux, and especially Gnome.

[andar]

How many torrents do you have in your session?

What plugins are enabled?

[jarlath]

This behaviour has actually stopped since I restarted Deluge, but for the record - I have 45 torrents, 10 of which are paused. I have the Speed Limiter, Torrent Files / Notification / Peers / Search enabled.

[yupotem]

This happens to me too.

Ubuntu Gutsy with 0.5.8.3, Athlon XP 1500+

If you have had Deluge running for a while in the system tray, say a day or two. Trying to bring back the main window from the system tray icon will cause deluge to spike to 100% CPU for 30 seconds to a minute. Once the Window appears highlighting a torrent will cause the same spike, or even restoring the deluge window from a lost focus will do the same.

I'm only using the Torrent Files and the Torrent Peers plugins.

Edit: I forgot to mention I have 8 torrent files, with 7 seeding and 1 finished.

[b3rx]

it happend to me once or twice. disabling torrent peers seems to stop this occasional locks up. im using slackware + dropline GNOME

[bugsbunny]

I'm in the middle of a lock up right at the moment. Debian lenny+sid. Dual processor (not dual core) 64 bit. The last time I got in I went and turned of the peer plugin, but it doesn't seem to have helped.

Note that this has been running for a few days now without problems until earlier today. Seeding a lot of torrents (about 100 at the moment), although most of them have no peers.

One of the 2 cpu's is spiking up to 100%, the other one is apparently unaffected. I'm going to try restarting it - if I can get all the torrents in a paused state first (otherwise the tracker will give me grief when I come back up).

[markybob]

I'm in the middle of a lock up right at the moment. Debian lenny+sid. Dual processor (not dual core) 64 bit. The last time I got in I went and turned of the peer plugin, but it doesn't seem to have helped.

Note that this has been running for a few days now without problems until earlier today. Seeding a lot of torrents (about 100 at the moment), although most of them have no peers.

One of the 2 cpu's is spiking up to 100%, the other one is apparently unaffected. I'm going to try restarting it - if I can get all the torrents in a paused state first (otherwise the tracker will give me grief when I come back up).

is this only happening when deluge has been minimized for long periods of time? is that right?

[bugsbunny]

I'm in the middle of a lock up right at the moment. Debian lenny+sid. Dual processor (not dual core) 64 bit. The last time I got in I went and turned of the peer plugin, but it doesn't seem to have helped.

Note that this has been running for a few days now without problems until earlier today. Seeding a lot of torrents (about 100 at the moment), although most of them have no peers.

One of the 2 cpu's is spiking up to 100%, the other one is apparently unaffected. I'm going to try restarting it - if I can get all the torrents in a paused state first (otherwise the tracker will give me grief when I come back up).

is this only happening when deluge has been minimized for long periods of time? is that right?

That's a possibility. I won't flat out state that that's the case though, because I'm not sure. I will say that once it's in a lock-up state then keeping it unminimized doesn't help. Note that although it was running minimized for extended periods it wasn't running minimized the entire time. I was bringing it up at times.

[markybob]

That's a possibility. I won't flat out state that that's the case though, because I'm not sure. I will say that once it's in a lock-up state then keeping it unminimized doesn't help. Note that although it was running minimized for extended periods it wasn't running minimized the entire time. I was bringing it up at times.

please try to test this and get back to us. i still havent been able to reproduce it, but i'll keep trying.

[bugsbunny]

Haven't been able to reproduce it, but some more info that may help you track it down. Or maybe not

Anyway the actual torrents go to a removable drive in my setup (the torrent files themselves are stored on the regular drive, along with configs etc). So I accidentally managed to unplug the external drive. This led to the following:

after a time O got a string of "torrent paused unable to access file" type messages. It seemed to get through these in fairly quick order. After cycling through these it then froze up again for a time (which I think may be related to how many torrents there are = guess on my part) and then it started with the messages again.

So the lockups take place even if the actual files aren't available. This leads to another point.

When deluge puts up a message stating "pausing torrent . . ." it would be nice if it actually attempted to change the status and actually pause the torrent rather than just retrying it ad infinitum after a short delay.

Also, if deluge is stopped with active torrents in process if the "always start torrents in paused state" setting is checked then, IMHO, when the program is restarted those torrents should be in a paused state.

2 more items (that should probably go in a separate post in the development section):
It would be nice if there was a "stopped" state, which basically means that no processing of any kind takes place against that item.
I would also be nice if there was a queued state that works like azareus' that will cycle through and place them in an active state only if there's peers that need servicing. If there's no peers then it acts as though it's in a paused state.