aMule Forum
English => en_Bugs => Topic started by: thedude0001 on January 11, 2005, 03:17:55 PM
-
Hi!
I have amule 2.0.0rc8 running under Debian SID and it keeps on eating up more and more memory.
This is the output of top after 2 days:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1009 dude 15 0 313m 117m 22m S 19.8 47.1 503:29.97 amule
and that's 12 hours later:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1009 dude 16 0 382m 137m 22m R 17.9 55.0 733:15.96 amule
It just doesn't stop, it keeps on getting bigger and bigger... :(
I've got 40 files in my download with a total size of around 10GB so this shouldn't be too extreme. And rc7 didn't show this evil behaviour with the same files.
-
i have 2 reasons:
1. gtk2
2. verbose enabled
which is the right one?
cheers
-
Verbose is disabled (you mean the setting under preferences, don't you?).
gtk... erm... good question, I didn't compile amule myself, I just installed it via apt-get (forgot to mention that in the original post). So I'm not really sure about this...
-
yep, verbose in amule tweaks.
well, try to find out what wxgtk is used now in debian for amule.. that might be the reason
-
dude@server:~$ sudo apt-cache show amule
Package: amule
Priority: optional
Section: x11
Installed-Size: 6872
Maintainer: Julien Delange
Architecture: i386
Version: 1.2.6+rc8-1
Depends: libatk1.0-0 (>= 1.7.2), libc6 (>= 2.3.2.ds1-4), libcurl3 (>= 7.12.3-1), libgcc1 (>= 1:3.4.1-3), libglib2.0-0 (>= 2.4.7), libgtk2.0-0 (>= 2.4.4), libidn11 (>= 0.5.2), libpango1.0-0 (>= 1.6.0), libpng12-0 (>= 1.2.8rel), libssl0.9.7,libstdc++5 (>= 1:3.3.4-1), libwxgtk2.5.3 (>= 2.5.3.2), libx11-6 | xlibs (>> 4.1.0), zlib1g (>= 1:1.2.1)
I think this means it uses wxgtk2.5.3, right? So, off to manual compilation without gtk2?
-
So, off to manual compilation without gtk2?
aye.. might help ;)
-
OK, took me some time to figure out that the Debian wxwidgets is linked against GTK2 and i have to compile them myself, too. After that wxwidgets 2.5.3 decided to constantly crash on me whenever hitting the "OK" button in amule preferences, so back to 2.4.2...
Somewhere in the process I decided to go with amulecvs (20050111) instead of rc8 and after some hours I finally got my mule up and running... Quite a learning experience, I think I have made almost every mistake you can make so I will be able to avoid them in the future. :D
First result:
Started off using 47 MB of ram, 12h laters 51 MB. So it seems the problem is solved (or better: found and worked around) and I will continue compiling my amules myself instead of just apt-getting them. :)
-
Originally posted by thedude0001
OK, took me some time to figure out that the Debian wxwidgets is linked against GTK2 and i have to compile them myself, too. After that wxwidgets 2.5.3 decided to constantly crash on me whenever hitting the "OK" button in amule preferences, so back to 2.4.2...
Somewhere in the process I decided to go with amulecvs (20050111) instead of rc8 and after some hours I finally got my mule up and running... Quite a learning experience, I think I have made almost every mistake you can make so I will be able to avoid them in the future. :D
First result:
Started off using 47 MB of ram, 12h laters 51 MB. So it seems the problem is solved (or better: found and worked around) and I will continue compiling my amules myself instead of just apt-getting them. :)
maybe contact the debian maintainer and try to get this solved for all debian/amule users?
if possble?
-
click (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285748)
i did it already.. but no response