Hi all,
I was hoping this memleak bug was fixed in wxGTK v2.8 (if indeed it is there and not amule monolithic) but I just got it by it again after an uptime of 24 hours. Here is the top output I managed to capture before killing amule:
20:05:55 up 1 day, 27 min, 6 users, load average: 22.20, 29.16, 32.42
Tasks: 209 total, 14 running, 195 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.2%us, 99.1%sy, 0.0%ni, 0.0%id, 0.1%wa, 0.1%hi, 0.6%si, 0.0%st
Mem: 2074936k total, 2025640k used, 49296k free, 796k buffers
Swap: 1020116k total, 1020116k used, 0k free, 4948k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3743 xxxxx 20 0 2493m 1.8g 440 R 17 89.6 216:59.54 amule
0164 xxxxx 20 0 200m 1080 444 S 10 0.1 63:20.15 audacious
221 root 15 -5 0 0 0 D 12 0.0 10:06.68 kswapd0
5317 xxxxx 20 0 110m 5676 996 D 7 0.3 40:17.46 k3b
3291 root 20 0 110m 35m 232 R 6 1.7 73:50.54 X
10164 xxxxx 20 0 200m 1124 488 S 10 0.1 63:22.28 audacious
3648 xxxxx 20 0 56948 1528 400 D 6 0.1 4:00.23 gnome-netstatus
Here, FWIW, is the cas output:
aMule CVS Fri Nov 9 07:01:54 CET 2007 has been running for 23:03 h
xxxxx is connected to ### xxxxxx ### [xxx.xxx.xxx.xxx] with HighID | Kad: ok
Total Download: 2.08 TB, Upload: 3.90 TB
Session Download: 1.99 GB, Upload: 1.10 GB
Download: 37.4 kB/s, Upload: 21.2 kB/s
Sharing: 853 file(s), Clients on queue: 925
Time: Nov 26 2007, 20:23
As I have indicated before, this bug does not occur with amuled.
$ rpm -qa | grep wx
wxGTK-2.8.4-6.fc8
wxGTK-devel-2.8.4-6.fc8
wxGTK-gl-2.8.4-6.fc8
compat-wxGTK26-2.6.3-8
$ uname -r
2.6.23.1-49.fc8[code]
[/code]