Crashing on VISTA + a few issues

[trektorrents]

Hey guys,

Thanks fro continuing the work on this fine app. I'm using:

Windows VISTA Home Premium, Core 2 2.0 GHz, HP Pavilion.

Deluge 1.2_RC_4 Runs fine (RC_3 would not run, the GUI opened, but nothing worked.)

I'm getting some random "Deluge has stopped working and windows has been forced to close it" errors. They happen doing mundane tasks in the GUI.

I've had it happen when:

Changing labels.
Scrolling up and down in the sidebar.
Changing from paused to seeding.

I also get a few torrents sticking on "checking" when starting after a crash. If I "pause" then "resume" all the torrents seed properly. They don't actually check the hash data, they just say 'checking'.

Finally, I get some Port issues. Either via uPnP or manual port forwarding, some files will not be "connectable" even while all others (out of several hundred) are fine. Port checks at online sites show the port open. And, finally, when clicking the "test active port" there's no icon to show open or closed in the Options menu for Network.

If there are any logs or particulars I can provide, let me know. Thanks.

[trektorrents]

Been working on this for a week, and have some progress.

The connectivity seems to be related to starting or unpausing a large number of files at once. For example, if there are 100 paused files, and I right click and "Resume All" one or two may get a tracker response error. This is seen by some trackers as unconnectable. Simply manually updating the file's tracker clears this.

Also, testing the port, for example on the

http://www.deluge-torrent.org/test-port.php?port=XXXXX

or

http://www.utorrent.com/testport?port=XXXXX

often shows the port closed, by a refresh of the page will show a connection and an open port, as if the check was 'waking' the response.

Still some of the old time issues.

An incomplete fileset (i.e. "Do not download" has been selected for some portions) means the file size shows as 0 in the main Gui, rather than the actual file size of the whole. But these are ongoing issues the app has always had.

Again, if any logs or other info are of help, let me know.

[trektorrents]

I have been able to reliably replicate one of the crashes.

I add a torrent, and use "Add in Paused State."
The torrent is added, with 0% shown.
I force a recheck.
While rechecking, I use right-click to add a label.

Deluge crashes.

Windows VISTA Home Premium, 32-bit.

[trektorrents]

As a follow-up:

The main issue with connectability seems to relate to the number of torrents made active at one time.

I've tried this on a private tracker:

30 torrents, all in paused state. Start all, and one or more gets a tracker error, and the tracker shows not connectable.
If 3-5 are started at a time, they all connect, and the tracker shows fine.

It's reproducible, easily.

[andar]

As a follow-up:

The main issue with connectability seems to relate to the number of torrents made active at one time.

I've tried this on a private tracker:

30 torrents, all in paused state. Start all, and one or more gets a tracker error, and the tracker shows not connectable.
If 3-5 are started at a time, they all connect, and the tracker shows fine.

It's reproducible, easily.

Maybe the tracker is dropping your announces due to some sort of throttling mechanism.

[trektorrents]

I'd say that was likely but in three other clients (uT, Az, Halite) I can pause/unpause 270 torrents at a time with no connectivity issue.