aMule Forum
English => en_Bugs => Topic started by: myth on January 13, 2010, 07:33:13 PM
-
I know my report sucks, but I haven't any data!
I just came back home and everything ok.
Then called aMule back from tray and all was laggy/slow. So I checked the processes, and aMule's CPU usage was normal ~5%.
But I saw Xorg's CPU usage grows up to 90% when I maximize aMule. As I minimize it the load goes back to normal values, ~2-5%.
What could it be? Mybe I should restart aMule...but yet after 4 days of runtime? Strange...
Up/Download works very well, just as normal.
(sys is Linux Mint 8 "Helena" 32 Bit )
-
But I saw Xorg's CPU usage grows up to 90% when I maximize aMule.
Does that change if you select a different tab?
-
No, unfortunately...
I restarted it just now...and all is normal :)
I'll see if after some longer runtime it changes...
-
I'll see if after some longer runtime it changes...
Longer runtime most likely means longer log. Unfortunately currently the whole log is kept in memory, which can produce significant X load.
-
Ahh...
Myth, do you have any debugging options on that write an insane amount of log messages?
-
From my experience, UPnP writes frequently (like every 20 minutes or so) to the log. In my case, I have 2 UPnP enabled devices (my router and a print server, which does not disable UPnP no matter what) and for every device it writes like 20 lines of log. I also notice slow X behavior after about a week or so. Running CentOS 5.4 and aMule 2.2.6
Regards.
-
Same here, with UPnP disabled.
-
Can't believe it's for log...after 1 day I have just 20 lines total.
I don't use uPnP ;)
My ./configure line is: ./configure --enable-optimize --disable-debug --enable-geoip
-
What about disabling statistics?
-
Hmm why?
Are they also kept in memory? If so, can't we change it to be written to a file every 5 hours (or some other time)?
Am I the only one letting aMule run for long time? :D
-
No, they are not. But your Xorg is choking, which makes me think something in you X / font / acceleration / etc etc libraries is having a very hard time dealing with stuff. I really, really doubt this is aMule's fault, but it would be interesting to know which part of it is affecting Xorg. Blending and drawing in statistics comes to mind.
-
Ah, ok....so I'll try disabling them when it get's heavy load ;)
-
Is blending and drawing done always? I never switched to stats tab, so if it's not done continuously, how can it affect the system, and if it's done constantly, why? At least before the first switch to this tab, it's not needed to draw all this. The data is available, so it could be only drawn when viewing it.
-
Well....after 4 days of runtime, exactly the same thing!
Maybe I'll try to make a build without stats, or was it simply in options?
-
On Windows there are "GDI handles" that like to run out. Is there something similar on X?
You are running SVN?
Just on a remote chance: compile without GeoIP.
-
Yes, I'm running SVN (9947 atm).
Now I just try without GeoIP!