Azureus 2.3.0.0 Resource hog

[ZimZum]

Just a heads up to people using Azureus BT client. The new update eats up 100% CPU resources and eventually just locks up completely.

 

[Czar]

updated this morning, seems fine, apart from the global torrent network thingum, wish I could shut it off, and at least declare which one is supposed to be shared and which not

 

[TheOmegaCode]

That's one of the 'common errors' listed on the site. There are also ways of fixing that.

I updated this morning also, and haven't had a single problem yet.

 

[alm4rr]

http://developers.slashdot.org/develope.../03/0458256.shtml?tid=95&tid=230&tid=8

 

[screw3d]

It's the opposite of me.. 2.3.0.0 has been great so far! Earlier versions will cause occasional (often) CPU spikes, especially when I try to open the client. Had to restart it once in a while

It's been running for hours now and I haven't experienced any CPU spikes so far :thumbsup:

/crosses fingers

 

[fs5]

I updated now my downloads don't work.. it's as if my ports aren't forwarded. However UPnP states they are:
I wish I could revert back to the old one. The wiki is also down so I can't check if this is a common problem.

Mapping request: UDP tracker client port (UDP/6881), enabled = true
Mapping request: Incoming Peer Data Port (TCP/6881), enabled = true
Mapping request: TCP Tracker Port (TCP/6969), enabled = true
Mapping request: TCP SSL Tracker Port (TCP/7000), enabled = false
Mapping request: UDP Tracker Port (UDP/6969), enabled = false
Mapping request: Distributed DB (UDP/6881), enabled = true

...

Mapping UDP tracker client port (UDP/6881) already established
Mapping Incoming Peer Data Port (TCP/6881) already established
Mapping TCP Tracker Port (TCP/6969) already established

 

[fs5]

updating to java 1.5 now seeing if that will help.

 

[Liviathan]

If it ain't broke don't fix it. 2.2.2 works fine for me...staying with it.

 

[fs5]

will update when I get home. had to reset my home computer after upgrading to 1.5.. now remote desktop is fubar'd

 

[us3rnotfound]

Alright thanks for that heads up, chief :roll:

 

[fs5]

Originally posted by: us3rnotfound
Alright thanks for that heads up, chief :roll:

look, I'm just posting here so if anybody else has the same problem they'll know what to do :roll: it's called being useful and not neffing.

Anyway, upgrading to java 1.5 did the trick. I also turned off the distrubted tracker until someone actually uses it.

 

[BillyBatson]

i LOVE Azureus and have had no problems with it... UNTIL NOW! i had a 16 day uptime and a total uptime of 47 days... until i updated to the new version! now in the last 12 hours Azureus has crashed 3 times!!!!! and not the crash where it tells you it's gone down, but where it crashed hours ago and i think it is sitll running until i try and click on the tray icon and the icon disapears only for me start it again and it tell me "Azureus didn't shut down tidily"
yes i have the updated java
DON'T UPGRADE!

 

[SleepWalkerX]

i've went along with the betas and have had no crashing. the only problem i had was with netlimiter. when i had it running it would conflict with azureus in that azureus would give these annoying error messages about "repairing x keys.." but i don't really need netlimiter cause azureus has a built-in limiter and i could just as easily get du limiter.

 

[rh71]

It's not taking up 100% CPU resources but it's definitely eating more memory by a slight margin. Along with that, it's not fully supported by some trackers I use so I need version 2.2.0.2 back... anyone know where to get it ?

EDIT>> Found it here

 

[Gurck]

I've had no problems with it at all, and it's eating less ram than previous versions. Not hogging CPU either. You have the latest java build?

 

[rh71]

Originally posted by: Gurck
I've had no problems with it at all, and it's eating less ram than previous versions. Not hogging CPU either. You have the latest java build?

I do. But I noticed it was using at least 30MB more RAM than the previous version on just about the same amount of torrents. It's no surprise with the new features they added like the swarm info. Still, not necessary and I didn't see any performance gain with it so I went back.

 

[Gurck]

I dunno... I recall it routinely eating over 200mb ram with just a few torrents open when I used it more frequently a while back. It's using 137 right now, with 19 torrents running. CPU usage between 18-30% with it and other things going (a/v, for instance).

 

[JACKHAMMER]

I updated, now I can connect to the tracker --- but I never d/l anything