New User - Having some crash-related issues

[Vampire337]

Hello all, new Deluge user here. I've recently decided to try out Deluge (1.3.5) running on a Windows 2008 R2 Server OS, with an Intel i5, 8GB RAM and around 8TB of disk space. Previously I used uTorrent until I upgraded my internet speed and (long story short) found out it was a horrible torrent client. I've since switched to Vuze, and it's been solid, but a couple trackers refuse to allow it. Rather than ditch two trackers I otherwise like, I'm trying out Deluge.

So I've installed Deluge and start adding torrents that are still running in uTorrent. I added around around 80 torrents in two folders, and Deluge crashed on me once during the checking of data. I had changed some preferences (Use Full Allocation, automatically add torrents from a folder, default data location, and a few others) which were lost and had to be set again. I expected that when I hit Apply or Okay Deluge would write to a configuration file which would load on next Deluge startup, but maybe this is not the case?

I added the torrents that were previously seeding in uTorrent. 66 were in one folder and 15 in another. I waited for them all to finish re-checking. I selected the 66 and selected "Move Storage", and moved them to the same folder as the 15. They all moved at once instead of asking me to select a folder individually (HUGE plus over uTorrent, as I intend to move about a thousand torrents to help consolidate my storage). Unfortunately, after all files had moved, Deluge crashed again. Ugh. I restarted it, and it remembers the 66 files in their original location, and by default they're trying to redownload, (which doesn't look too great for my tracker ratio). I tried moving the files again from the old location to the new, and apparently Deluge overwrote the valid data with empty data, WITHOUT ASKING ME IF I WANT TO OVERWRITE DATA?? Yikes. I stopped Deluge and tried manually copying the data back to the old location, and it appears that some of it is not lost, (tho I've still lost a few GB, that's not a huge deal I guess).

So, Deluge looks like it has promise, but I'm a little surprised at some of what I would think is basic flaws, or maybe I'm doing something way wrong, and wanted to see what advice the community might offer. Is there any logging to help me determine the cause of the random crashing? Is there a way I can force it to write the preferences changes to disk so I don't lose that when it does crash? Is there a way to trigger Deluge writing to its own internal data when moving files, so that can ride through a crash and help me avoid losing data in the future?

[Vampire337]

Update: I've figured out that the files were not moved anywhere to overwrite anything... Whew. Windows had asked me if I wanted to overwrite the files (I already told it to merge the folders) and I didn't hit Okay yet. So no worries on overwriting everything, as apparently there is no option to overwrite anything. But I'd still like to know why it's crashing (couple more times since my first post), and what I can do to make it keep settings like what columns I want to view for the downloads (I would like to see tracker status and data location by default, as I do in the other clients)

Also, I tried moving files to a new location (a test folder with nothing in it), and then I made sure not to touch it for a few minutes. Then I went to preferences, and enabled send usage data, and then crashed again. Upon restart it appears to have remembered the new folder location for all 81 torrents (this time).

[Vampire337]

So, my first 24 hours with Deluge and I really like the client interface and its features. Unfortunately, the fact that it crashes very regularly makes it pretty much unusable. Also doesn't look like a lot of life here at the support forums, which is fine since this is a free product. If anyone has any thoughts, I'd love to see this one work, but it looks like an inherent memory-leak-type-issue causes it to take on too much water to stay afloat for an hour, let alone for a few months.

So I'm off to try out something else. Good luck!

[Cas]

It is likely that if you are leaving the gtk ui window open for a long time it may well crash as there is bug that has been mentioned by Windows users but we have no solution as it is a gtk issue. The solution is to run deluged separately, then if you untick Classic Mode in gtk ui preferences you can connect to the running deluged. I have discussed this many times so although the forum is not very active searching previous posts should give up some clues.

[Vampire337]

Being that I was unaware it was a gtk issue, I wasn't very effective at searching, although I promise I did search for several variations of "random crash" and "memory leak" with nothing that seemed to point me in the right direction.

Ultimately it sounds like I came to the right conclusion; unfortunately this one won't do what the other clients do, so I'll continue looking for something that will be a better fit. Thanks for the info, Cas!