aMule Forum
English => en_Bugs => Topic started by: BonnyFused on February 18, 2005, 09:33:20 AM
-
Hello all!
I noticed a (strange) behaviour on aMule 2.0.0-rc8 (I don't know if it was the same with the past RCs because I didn't notice it): after leaving aMule running for some days, it's memory usage has grown up to over 300 MB! 8o
Is this a normal behaviour? Why does this happen and how would it be possible to limit this memory hungriness?
Thank you in advance...
-
This is usualy not a bug in amule but in wxgtk / gtk.
Which wxgtk is installed on your computer? And against which gtk is it linked?
-
BonnyFused,
Either way, rc8 had some memory leaks that are now fixed, but I have never seen a report about eating tons of memory. Please try a recent CVS tarball if you can.
Cheers!
-
Originally posted by thedude0001
This is usualy not a bug in amule but in wxgtk / gtk.
Which wxgtk is installed on your computer? And against which gtk is it linked?
I don't know, but if you tell me how to check these things, I'll be glad to post my situation!
Thanks...
-
Ah, as you now added "Debian SID" to your profile I can see that this is the root of all evil. :) I ran into the exact same situation on Debian SID back when rc8 came out, amule eating up tons of memory which was in fact wx...
If you are not afraid of some compiling the best thin IMO qould be to 'apt-get remove' all libwx packages (you can see which ones are installed if you enter 'dpkg -l | grep libwx | grep ii' as root in a console). Then get wxGTK 2.5.3 from here (http://www.wxwidgets.org/dl_gtk.htm#dev) and compile / install it as explained in the wiki: http://www.amule.org/wiki/index.php/Compilation_Installation
When that is done you can go on to compile your amule, a guideline for Debian is here: http://www.amule.org/wiki/index.php/HowTo_Compile_In_Debian Of course you have to leave out the libwx*-packages as you installed wxGTK yourself for that. It may be a bit tricky at the first time, but once you got it done it is easy to do again ;)
And if you are into the latest development you are free to try our daily CVS snapshots provided here: http://amule.hirnriss.net/
If you get stuck somewhere feel free to ask here. I hope I didn't get anything wrong from my memory as I switched my server from Debian to Gentoo some weeks ago...
-
Originally posted by thedude0001
Ah, as you now added "Debian SID" to your profile I can see that this is the root of all evil. :) I ran into the exact same situation on Debian SID back when rc8 came out, amule eating up tons of memory which was in fact wx...
Can you tell me in which way it's a wx problem and how we (or you) could be helping wx to get rid of that? I mean, it would be useful for all other Debian SID users to have a working wx... or not?
-SNIP-
If you get stuck somewhere feel free to ask here. I hope I didn't get anything wrong from my memory as I switched my server from Debian to Gentoo some weeks ago...
I'll try it ASAP, just tell me if it would be easy to remove all the stuff I'll be installing while compiling from source, if I ever would like to use .debs again.
Thanks...
-
Uninstalling a self compiled amule is quite easy, just go to the sources directory from which you installed amule and type (as root) 'make uninstall'. Uninstalling a self compiled wx isn't just as beautiful, make uninstall doesn't work here, but there is a 'quick and dirty' guide in the wiki: http://www.amule.org/wiki/index.php/How_to_uninstall_wxWidgets
About helping the wx devs: Work in this direction is being done, our devs are hunting down memleaks in the wx sourcecode and supply patches to the wx devs which then make it into their cvs tree (where the development is done) and then are tested by /among others) amule users, devs and testers.
-
Originally posted by thedude0001
Uninstalling a self compiled amule is quite easy, just go to the sources directory from which you installed amule and type (as root) 'make uninstall'. Uninstalling a self compiled wx isn't just as beautiful, make uninstall doesn't work here, but there is a 'quick and dirty' guide in the wiki: http://www.amule.org/wiki/index.php/How_to_uninstall_wxWidgets
Du weisst ja aber alles, hast fuer alles eine Loesung! :) Toll! ;)
About helping the wx devs: Work in this direction is being done, our devs are hunting down memleaks in the wx sourcecode and supply patches to the wx devs which then make it into their cvs tree (where the development is done) and then are tested by /among others) amule users, devs and testers.
OK, get down with it... :) And, if you feel I could be helpful, just ask...
Gonna try to install from source tonight! ;)
-
... if I remove (apt-get remove --purge amule) the installed program and want to use the compiled one, what will happen to the partial downloaded files and my credits file? In general, what about my settings?
Thank you.
-
Partial downloads will not be touched in any way as they are not a part of the package. If you uninstall it with --purge apt-get will delete all config files and I think that includes the credits and your userhash. I'm not too sure about it whether apt-get will only remove the config files it installed in the first place (which would leave ~/.aMule/ and ~/.eMule where it is as they are created by amule on the first startup) or if it removes them all.
My advice would be to 'apt-get remove amule' (without --purge). This leaves your config etc. where it is and your freshly compiled amule will just start reusing it without any trouble.
-
So here I am, back again!
For wxGTK I had to install:
zlib1g-dev
libpng12-dev
libjpeg62-dev
libtiff4-dev
libgtk1.2-dev
from the last one, the following were installed too:
libglib1.2-dev
libx11-dev
libxext-dev
libxi-dev
libxv-dev
x-dev
x-libs-static-dev
(it's a bit of a reminder for those who eventually will search this forum).
Gone forth with "make", "make install" and "ldconfig".
Same thing for wxBase.
For aMule I needed:
libcurl3-dev
libidn11-dev
libssl-dev
./config is done, then...
... after typing "make" I get this error:
make all-recursive
make[1]: Entering directory `/home/bonny/amule-cvs'
Making all in m4
make[2]: Entering directory `/home/bonny/amule-cvs/m4'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/bonny/amule-cvs/m4'
Making all in intl
make[2]: Entering directory `/home/bonny/amule-cvs/intl'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/bonny/amule-cvs/intl'
Making all in po
make[2]: Entering directory `/home/bonny/amule-cvs/po'
rm -f en_GB.gmo && : -c --statistics -o en_GB.gmo en_GB.po
mv: impossibile fare stat di `t-en_GB.gmo': No such file or directory
make[2]: *** [en_GB.gmo] Error 1
make[2]: Leaving directory `/home/bonny/amule-cvs/po'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/bonny/amule-cvs'
make: *** [all] Error 2
Need help! :baby:
-
You need gettext and gettext-devel packages
-
Originally posted by GonoszTopi
You need gettext and gettext-devel packages
OK:
apt-get install gettext
did it.
Now, I guess it ain't related to aMule, but I get:
The font "-monotype-arial-medium-r-normal-*-14-*-*-*-p-*-iso8859-1" does not support all the required character sets for the current locale "it_IT@euro"
(Missing character set "ISO8859-15")
(Missing character set "ISO8859-15")
Initialising aMule
Userhash loaded: 2C4195F6070E0DB8CDF1D9622C3F6F22
The font "-monotype-arial-medium-r-normal-*-14-*-*-*-p-*-iso8859-1" does not support all the required character sets for the current locale "it_IT@euro"
(Missing character set "ISO8859-15")
(Missing character set "ISO8859-15")
The font "-monotype-arial-medium-r-normal-*-14-*-*-*-p-*-iso8859-1" does not support all the required character sets for the current locale "it_IT@euro"
(Missing character set "ISO8859-15")
(Missing character set "ISO8859-15")
The font "-monotype-arial-medium-r-normal-*-14-*-*-*-p-*-iso8859-1" does not support all the required character sets for the current locale "it_IT@euro"
(Missing character set "ISO8859-15")
(Missing character set "ISO8859-15")
*** reading servers
Any help 'bout this?
Cheers! ;)