aMule Bug Tracker - aMule
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000987aMuleExternal Connpublic2006-10-09 21:002008-07-09 16:29
Reporterancechu 
Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionopen 
PlatformOSOS Version
Product Version2.1.3 
Target VersionFixed in Version 
Fixed in Revision
Operating SystemMandriva Linux 2007.0
Summary0000987: Full CPU usage after a couple of minutes
DescriptionAfter some minutes of functioning, amule eats all the CPU available and the download rate goes to zero. If I launch amule from the command line I can see lots of messages,

(amule:11389): GLib-WARNING **: poll(2) failed due to: Argument invalid.

(The number in the parenthesis can be different)
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2006-10-09 21:00ancechuNew Issue
2006-10-09 21:00ancechuOperating System => Mandriva Linux 2007.0
2006-11-06 12:24carstenNote Added: 0002146
2007-07-17 17:55maciasNote Added: 0002359
2007-07-23 17:09KryNote Added: 0002364
2007-11-22 14:47garvintNote Added: 0002461
2008-07-09 16:29WuischkeStatusnew => closed

Notes
(0002146)
carsten   
2006-11-06 12:24   
I have the same problem. The CPU-usage raizes to 100% and I have to kill the process.

OS: Tiger 10.4.8
aMule: 2.1.3
(0002359)
macias   
2007-07-17 17:55   
In my case it is a rare situation, but it happens unfortunately -- I left several times my computer with amule running, and when I get back it was all hot, fans running at hi speed, CPU at 2GHz and nothing indicated it was necessary. When I quit amule CPU dropped to 800MHz.
Does aMule do some background computation? Upload/download was normal, no new big/rare/whatever files were added, or just downloaded (when they are checked).

I run amule in full debug mode (via gdb).
(0002364)
Kry   
2007-07-23 17:09   
is this amule or amuled?
(0002461)
garvint   
2007-11-22 14:47   
Have amule and the problem is similiar. CPU goes to 100% while its running, can drop briefly to 30% but hogs the whole system generally.can gdb fix this?