So I was in the process of hashing a lot of stuff. But one folder was frozen on 3% for several hours. Eventually I found out that OneSwarm got the java error "out of heap space" or something of the sort, had copied the message but Azureus gave some error message about it not closing properly and stole my clipboard after i double clicked on the "this message will close in 12 seconds" text. Retarded thing ("feature?").
So I thought I'd just restart OneSwarm.
It didn't close after several minutes. So I just killed the process, should be no problem in well-written applications.
BUT when I launched OneSwarm again the hashing queue is empty! Nothing is hashing. Ok great. Fucking not. I just hope the application has brains enough to skip the files it has already shared if I try to has the subfolders again..............
Ok after a test, yes and no. It appears to NOT add duplicate torrents however only AFTER it has hashed the folder again. So this means that I have to rehash 300 of my 600 folder queue before the new folders will be added? Oh yeah, I forgot about the memory problem, the same thing will happen and I have to force-close the application again and lose the queue plus lose several hours of my time.
How hard would it have been to save the paths to be hashed in a text file and just remove the top line after it has been hashed? Not very hard at all.
OneSwarm needs a better sharing system (and a proper non-browser GUI). Seriously.
This reminds me of something that happened to me before btw, when I forced-closed OneSwarm and opened it again all my fiends were gone. Too bad? And that was back when you had to add them manually one at a time. Wonder if it will happen again...