Opened 10 years ago

Closed 10 years ago

Last modified 5 years ago

#1920 closed bug (Duplicate)

Checking Torrent Stops at a Random Percentage on Windows

Reported by: WillyWolly Owned by:
Priority: major Milestone:
Component: libtorrent Version: 1.3.3
Keywords: Cc:

Description (last modified by Cas)

The checking of torrents stops suddenly on Windows. The problem occurs very often. It just stops checking at some percentage and refuses to continue. I have to close and start Deluge again for it to continue, but then it starts checking the same torrent again and stops at some point.

NOTE: I rolled back to 1.3.2, which does not have the problem. So this should be easy to trace back for you.

Also note that there is now a new status for torrents that are checking which is called 're-checking' (or something - I can't remember exactly), which is displayed as status sometimes instead of just checking. This could be related to this. Also in this version some torrents won't respond to pause/resume commands, which is related I think.

Change History (7)

comment:1 Changed 10 years ago by Cas

Is this with the old or new 1.3.3 Release? ReleaseNotes

comment:2 Changed 10 years ago by WillyWolly

It is the new one with the newly added in libtorrent 15.7, I reinstalled to be sure. I'm looking at a screen that shows a halted check now. By the way: I did an uninstall of Deluge, before installing 1.3.3, but I didn't remove the Deluge directory in Appdata, so all torrents and settings remain.

Other bugs that show there is something wrong with this release on Windows:

  • Closing the program is not clean: the taskbar icon just keeps saying 'Not connected'. I can't even kill the process with task manager ('Access Denied'), then it disappears out of itself after a few minutes. And when started again it starts checking even other torrents that it wasn't checking before.
  • Another bug that popped up: one of my torrents is now in error: says 'The parameter is incorrect'.


  • Actually, this release won't download or upload at all :-O. Though I must say from the many restarts I don't have many checked 'clean' torrents left.



If you're sure that these kind of bugs are libtorrent based, I guess there's not much we can do about it here, right? Just hope for libtorrent to fix this... Is everything alright under Linux?

comment:3 Changed 10 years ago by Cas

  • Component changed from other to libtorrent
  • Milestone changed from Future to 1.3.x

What version of Windows are you using and is it 32 or 64-bit?

And when started again it starts checking even other torrents that it wasn't checking before.

If deluge is not existing cleanly it can end up re-checking every torrent.

If you're sure that these kind of bugs are libtorrent based, I guess there's not much we can do about it here, right? Just hope for libtorrent to fix this... Is everything alright under Linux?

We updated 1.3.2 to lt 0.15.5 (from 0.14.10) and that is when the problems started. There are no issue like this with Linux, it seems to be only Windows.

comment:4 Changed 10 years ago by Cas

  • Description modified (diff)

comment:5 Changed 10 years ago by WillyWolly

I am using 64-bit Windows 7. You are right, 1.3.2 has the same problems (I said before that 1.3.2. was OK). But from testing, 1.3.3 acted even weirder: more torrents rechecking, the parameter error and the extra checking status above.

While we are well aware of 1.3.3 not functioning on Windows (look at all the forum posts in the Deluge forum), are the Libtorrent people aware of this??? Are other programs based on libtorrent affected as well? In other words, can we be certain that the problem lies with libtorrent?

comment:6 Changed 10 years ago by Cas

  • Resolution set to duplicate
  • Status changed from new to closed

I recently updated ticket #1956 to better track the libtorrent issues so I'll close this as duplicate.

comment:7 Changed 5 years ago by Cas

  • Milestone 1.3.x deleted

Milestone deleted

Note: See TracTickets for help on using tickets.