|
|
Hello to aMule team!
Thank you all for amazing work, I wish to hope that the project will be in active development, and that all errors will be fixed!
I confirm troubles with huge virtual memory eating. This applies equally to amule AND amuled. I use version 2.2.6 of both, and I think that unfortunately this problem is not reproducible, because amule (or amuled) can work several days without issues, and then suddenly begin eat all available virtual memory.
So I'm not able to give more information.
When this happens, system became entirely unresponsible (completely freeze), but it's still other problem (kernel bug 12309).
My system is:
Lenovo IdeaPad s10, Intel Atom N270, 1GB RAM, 1GB swap,
Ubuntu 10.04, kernel 2.6.32-22-generic,
dpkg -l amule*
ii amule 2.2.6+debian0-7
ii amule-common 2.2.6+debian0-7
ii amule-daemon 2.2.6+debian0-7
ii amule-utils 2.2.6+debian0-7
logs:
/var/log/syslog:
Jul 26 12:48:38 lenovo-laptop kernel: [16565.694804] amule invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0
Jul 26 12:48:38 lenovo-laptop kernel: [16565.694815] amule cpuset=/ mems_allowed=0
Jul 26 12:48:38 lenovo-laptop kernel: [16565.694828] Pid: 4579, comm: amule Not tainted 2.6.32-22-generic 0000035-Ubuntu
Jul 26 12:48:38 lenovo-laptop kernel: [16565.703737] Out of memory (oom_kill_allocating_task): kill process 4579 (amule) score 0 or a child
Jul 26 12:48:38 lenovo-laptop kernel: [16565.703747] Killed process 4579 (amule) |
|