Leaving Vuze running hangs machine

[Davesim]

I've been using Vuze for about 10 years & am a BIG fan, I generally leave Vuze running 24/7 but recently I've recently found in the morning my machine is frozen with very limited access to open applications. I can't open most programs (Outlook, Internet Explorer, etc) & when I try to restart the machine it hangs at logging off stage - leaving me to literally pull the plug.
My machine doesn't have any viruses (I think) but if I leave Malwarebytes Anti-Malware running at the same time I don't have the problem occur & if I don't leave Vuze running, once again no problem.

Is there a security breach in Vuze with the latest update? I tried changing the port but that also didn't make any difference.

I'm running:
Windows 7 Pro 64 bit, 8 gig ram i7 CPU
Norton Internet Security
Vuze 5.4.0.0
Java 1.6.0_43

Anyone have any ideas?


 

 

[parg]

Do you have a lot of torrents/downloads in your library? Just wondering if Vuze is somehow running low on (Java) memory when left running a while.

Can't imagine how running Malwarebytes at the same time would help though!

[GaryE]

I was thinking the exact same thing parg.  It sounds like he needs more java memory to me.  I mean there were older versions of vuze which had memory leaks that would crop up after leaving it running for 4 days or so but I have not experienced that in about 4 years so I doubt that [a memory leak] is the problem here.

Also if you leave some memory intensive process open in vuze it could also greatly increase the amount of memory you need.  Leaving statistics open for example sucks up a lot of memory over just a few hours.  I used to leave it open and I had to restart vuze every 20 hours or so.  Once I forgot to restart statistics and I went about 70 + hours without restarting and I did the math and only kept stats up when I wanted/needed them.  LOL

So if the original poster is doing something like that it might also explain the problem.

 

[Davesim]

I was thinking the exact same thing parg.  It sounds like he needs more java memory to me.  I mean there were older versions of vuze which had memory leaks that would crop up after leaving it running for 4 days or so but I have not experienced that in about 4 years so I doubt that [a memory leak] is the problem here.

Also if you leave some memory intensive process open in vuze it could also greatly increase the amount of memory you need.  Leaving statistics open for example sucks up a lot of memory over just a few hours.  I used to leave it open and I had to restart vuze every 20 hours or so.  Once I forgot to restart statistics and I went about 70 + hours without restarting and I did the math and only kept stats up when I wanted/needed them.  LOL

So if the original poster is doing something like that it might also explain the problem.

 

 

Hi Guys,
I think you may have hit the nail on the head. I was leaving open around 15-20 torrents, most were just queued as I'm on shitty Oz broadbad & about 6-8 seeding. I removed half of them yesterday & it didn't hang this morning!!!

With the Malware running I'd constantly get error messages popping up but it didn't stop Vuze downloading/uploading:

Detection, 7/09/2014 12:47:25 AM, SYSTEM, DAVE-PC, Protection, Malicious Website Protection, IP, IP Address, Port, Inbound, C:\Program Files\Vuze\Azureus.exe,
Detection, 7/09/2014 12:56:17 AM, SYSTEM, DAVE-PC, Protection, Malicious Website Protection, IP, IP Address, Port, Outbound, C:\Program Files\Vuze\Azureus.exe,

Cheers
 

[parg]

Be interesting to know how it categorises an IP address/port as being malicious - possibly it is just other peers out there that have been configured to use well known ports for their P2P traffic? e.g. 80, 443.

[ekstasee]

Yes, java memory was the first thing that came to my mind, however,  4 yrs ago on an older, lower-spec (read "ancient") machine, I had a similar problem occurring during the early hours of the morning.  The fix for that was higher-output PSU.  The reasoning I came to determine was that I DO run many hundreds of torrents and during the early hours of the morning when bandwidth availability was high (minimal traffic on the local public network) more torrents were using higher bandwidth resulting in higher CPU and HDD load, therefore when the loads peaked, the PSU couldn't cope and the whole shabang just crashed.  I tried many other other "fixes" b4 I reasoned that one through.  I think I also invented a few dozen new profanities!
 

[GaryE]

Be interesting to know how it categorises an IP address/port as being malicious - possibly it is just other peers out there that have been configured to use well known ports for their P2P traffic? e.g. 80, 443.

 

Most of those Maleware programs using something similar to the peerguardian/BTGuard list of "bad IP addresses".  The problem of course is that those lists have broad ranges of IP addresses used by the largest seedbox providers in the world.  For example all of them block OVH France.  Well since about 65% of seedbox providers in Western Europe are OVH resellers you have immediately eliminated a huge quantity of seedboxes (and there for potential seeds).  I suspect (but I do not know for certain) that these "Malicious Website Protection" address are simply that same list that BTGuard and peerGuardian have developed.

This of course does not even take into account the fact that the lists themselves are highly suspect.  There is actually a lot of evidence that the lists that those kind of programs use are actually more harmful to the bitTorrent community than they are good.  I mean it is not exactly hard for the "Malicious" folks out there to get a copy of whatever software and make sure they get an IP address which is not on the list.  It is not exactly rocket science.  LOL  For some reason a lot of torrenters buy into this type of product and think they are helping themselves . . . they pay through the nose for the product and all they really accomplish is to greatly narrow the pool of potential IP's that the anti-file-sharing nazis have to monitor to a much smaller number thus making file sharers easy to catch LOL  Or to put it another way . . . I have heard a whole lot more stories of people saying "I used BTGuard but I still got a notice from my ISP" than I have heard "Once I started using BTGuard I stopped getting notices".  By a lot I mean on the order of 10:1 or 20:1.  Seriously!

So the bottom line is that exactly how they determine that an IP address is bad is highly suspect at best and is down right deceitful at worst.  No one really knows for sure.  But again I hear a lot more credible accounts telling me they do not work than I hear credible accounts telling me they helped.