After experiencing this crash roughly two dozen times by now and manually restoring my automated backups because the .bak files Deluge creates disappear, I've concluded the integrated backup system, which sought to fix state losses in certain situations (e.g. spontaneous loss of power) is in fact ca...

If you haven't already, try the high performance preset offered by the ltConfig plugin. There should be an improvement right away, and from there you can customize it to your liking referencing libtorrent's documentation. The default libtorrent profile in Deluge is abominable and, unfortunately, it'...

A more detailed second window popped up upon termination this time.

Again, this is 1.3.12 py2.7.

I never experienced this crash on 1.3.11, but finally did on 1.3.12 today. My client did not crash--only the daemon on my server.

It was present. I have to amend what I said in a significant way: All that was lost this time was actually the fastresume file. Given that, the problem is certainly not "worse than ever". It's been a while since my state had corrupted in 1.3.11 so I forgot just how awful it was (in that ca...

In the past I've only lost my state or fastresume on dirty shutdowns of the PC. Today I woke up to find the client wasn't connected to the daemon. I went to the other room and found deluged (1.3.12) had crashed with an error saying VC+++ had requested an unexpected exit or similar. I wish I had the ...

Cache was already quite large at 100,000/3,600. I was under the impression that would only affect frequency of writes of download data and not how frequently fastresume is written to the state directory.

Very pleased with the command-line switch now

Wow. I had looked last year and turned up nothing. Thank you!

I've recently migrated my server's system disk to an SSD. This wasn't an issue in the past, but the 50 GB per day of writes to Deluge's AppData directory is excessive (over 18 TB per year) and will have a tangible impact on SSD life. There would be no problem if Deluge was at least somewhat portable...

Surely this is not intended behavior: immediately starting downloading of a torrent after recheck. It's made my migration from uTorrent far more annoying than it had to be. Especially problematic are large torrents I've downloaded only certain files from. I'd like to be able to recheck, sort by prog...