On 6/21/08, Cameron Dale <[EMAIL PROTECTED]> wrote: > On 6/21/08, Steve Cotton <[EMAIL PROTECTED]> wrote: > > I've seen this twice since upgrading to 0.1.7.
Thanks a lot for bringing this to my attention, I think it was more serious than I at first suspected. :) > Unfortunately it seems to be intermittent (if you > can reproduce it reliably, let me know), which makes it very difficult > to diagnose. Soon after I sent this, I discovered that I could reproduce it (hence the seriousness). I have committed a fix to it, and a new version will be available soon (probably today). FYI (don't feel like you have to read or understand this, I just felt like I owed you an explanation), this error only occurred when stopping an old long-lived torrent and then starting a new one with the same identifier hash. Since the adoption of the long-lived torrents, I was mistakenly still using the long-lived identifier for scheduling and removing tasks. This caused the removal of tasks from the stopping torrent to remove some tasks for the initialization of the new torrent since they use the same identifier, causing the initialization of the torrent to hang. I changed the task scheduling to use a unique hash for each torrent, and it seems to be working fine now. Thanks again, Cameron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
