#5 finished torrents are not removed.

open
None
5
2004-11-03
2004-10-27
Lasse Karstensen
No

I believe there is a locking issue in BitQueue/scheduler.py.

When a torrent is completed, ie. max_seed_rate is made, and
Scheduler.remove() is run, the thread stops.

self.lock.acquire() doesn't seem to return, and the whole thread
gets stuck. On the command line you see that the torrent
gets into 'finished 201%' and nothing more happends.

Tested on the latest release. Also present in earlier versions.

Discussion

  • Logged In: YES
    user_id=101538

    I'm not sure about this but I want to tell you that
    Scheduler.remove() is usually called manually by user.
    Whenever a torrent has finished, it is just paused by
    removing from controller.

     
    • assigned_to: nobody --> xgie