On 24 May 2012 14:30, remcl <
remus.c...@gmail.com> wrote:
> After i selected from the preferences the torrent folder to my folder where
> i keep torrents it started to lag humongously ("lightweight" my a$$)
Be interesting to know how many torrents you were asking it to add at
once that caused it to slow down so much.
> and decided to kill the process.
Never a good idea really is it, much like it's not really a smart idea
to pull the power cable out of computers. It sounds like it was in the
process of adding torrents to the session and then you killed it
before the core had a chance to save the state (which happens every 5
minutes). So it seems it would be sensible to force a flush of the
state to disk prior to removing the torrent file just in case someone
kills the process or computer whilst its in the middle of working.
Although this would also cause it to process torrents at a slower rate
due to the increased disk i/o so swings and roundabouts.
> After that i've seen almost half of my torrents missing and a search showed
> them in a crapudge, sorry, deludge folder with all their names in hex.
It moves the torrent file to a directory in the form
<infohash>.torrent. How else would you propose it handled the
situation? Is it supposed to leave them where they are and keep a list
of every single torrent filename it's ever auto added so it doesn't do
it again? Then you'd get people frustrated at how its not adding the
torrent. Seems like the easiest solution to me...
> System restore didn't solve the issue. I don't expect any help (I've
> read other bug reports of your crapware) just wanted to describe what
> happened.
You've done so with such elegance and detail that we'll surely be able
to resolve any future errors like it...
> That's the last time i'll use any more shit python or freenux garbage OR the
> garbage tracker sites that don't accept uTorrent.
>
Farewell!