aMule Bug Tracker - aMule
View Issue Details
0000220aMuleMiscpublic2004-12-05 16:022005-02-18 16:15
ibutler 
Kry 
normalmajoralways
resolvedfixed 
2.0.0-rc7 
SVN 
0000220: CPU usage critical on Log full
In Spanish:
Cuando aMule carga mucha informacion en la solapa aMule Log el uso de CPU se pone muy alto.
Yo parchee este problema en mi aMule para que tarde mas tiempo en ocurrir pero el error persiste.

in English:
When aMule charge too much data log in aMule Log tab the cpu usage gets critical.
I already remove some log from the ListenSocket to enlarge time until this ocurrs but the error persists.

SO: SlackWare Linux 10.0
Plataform: x86
CPU: Intel P3 1066Mhz
RAM: 512Mb
No tags attached.
Issue History
2004-12-05 16:02ibutlerNew Issue
2004-12-08 01:34KryStatusnew => assigned
2004-12-08 01:34KryAssigned To => Kry
2004-12-08 01:34KryNote Added: 0000425
2004-12-30 20:33ibutlerNote Added: 0000479
2005-02-18 16:15KryStatusassigned => resolved
2005-02-18 16:15KryFixed in Version => CVS
2005-02-18 16:15KryResolutionopen => fixed
2005-02-18 16:15KryNote Added: 0000652

Notes
(0000425)
Kry   
2004-12-08 01:34   
We mmust have a log limit. seems wither wx or gtk cause long, long cpu when log is big.
(0000479)
ibutler   
2004-12-30 20:33   
yeap!
i have already patched my amule. it's easy but is good that the project programmers know this problem.
May be, could be cool to have a log level and set it in preferences dialog or something like that.

Bye!
(0000652)
Kry   
2005-02-18 16:15   
Fiiiiiiiiiiixed. Was a bug from wxGTK, now gone.