Ghostfucker, Vuze . umm where's scape option lol
Printable View
anyone else having problems when torrent finishes and begins to seed, tracker shows that it's 97%(don't remember exactly the prosent, but close to 100%) and then in a few minutes, tracker shows that it's also 100% done and seeding? the leeching torrent is like a ghost.. i use bt spoof
The delay should be normal, but you mean the torrent is shown twice? Both as 97 and 100% done?
Can you check if it happens with another spoof? It's important to know this.
yes my scape is enabled.
It's rc4 with allowing unencrypted connections.Quote:
Quote:
Originally Posted by Grambo
I have the same problem on some torrents. With bt spoof.
Encryption settings?
Quote:
Originally Posted by ghostfucker View Post
yes, thats a known issue...
some clients* use a newer lte-protocol, but azureus has still the old implementation and can't understand some encrypted messages.
-> if you have the encryption enabled and use a client with the new protocol e.g. ut 1.8.1, azureus wont be able to connect to other clients, which have the new ltep implementation too.
*
- bittorrent 6.1.0, 6.1.1, 6.1.2
- deluge all versions
- halite 0.3.0.1, 0.3.0.2, 0.3.1.0, 0.3.1.1
- utorrent 1.8.0, 1.8.1
Bittornado is not on the list.
I'm running Ubuntu and I've managed to get mod 4.2.0.3 running, but torrents are forever stuck in "Waiting..." and I cannot see info pages when I double click on them. I can't seem to find a solution despite considerable effort. Any ideas as to what might be wrong?
(I've also tried many older versions hoping it was only a problem with the current release.)
It seems that this usually happens to me when I am running the Vuze extreme mod emulating an early version azureus. I had always assumed it was because I was running to many torrents and thus causing a strain on the framework of the java code during processor cycles. I would see 67-97 % Complete in the snatch list as well as 100 % complete on a different line, both with my username. The source of the preoblem could be different, but I made the assumption that I was "stressing" the client too much by running too many torrents at the same time and certain trackers recieving buggy annouces. I hope this helps some ? But you may have found something else. If so, give us some more details to pass to the coders. They need to check this out. Thanks and good luck. :wink:
I guess he meant a client full of running torrents leeching/seeding. Azureus can be easily overloaded, given the fact it already is memory hungry :biggrin:Quote:
what do you mean by overloaded client?