aMule Forum
English => aMule crashes => Topic started by: Ezeltje on January 16, 2006, 06:37:20 PM
-
I compiled the 2.1.0 source last Friday (the freshmeat.net rpms still have dependency errors) and have been running the new amule since then. Unfortunately, I have not been able to keep it alive more than a day or so without crashing. This is in marked constrast to v2.0.3 which never crashed (until I closed it to boot 2.1.0 its uptime was 100 days, although it did grow in memory size and was starting to slow my system down).
What kind of information can I provide to help you all figure out why 2.1.0 is less stable? Recompile with debugging and posting gdb backtraces?
FWIW, this is the wxGTK package I have installed: wxGTK-2.6.0-1 (from here).
I am running Fedora Core 4 with this kernel: 2.6.14-1.1656_FC4
-
the gdb backtraces would be the best solution yes
and maybe before taht update wxGTK to 2.6.2
-
I see that the only wxGTK 2.6.2 package on Berlios is source: wxGTK-2.6.2-i686-1thee.tgz
Forgive my ignorance, but does this need to be compiled or just unpacked into the /usr/.. directory tree?
Thanks.
-
no thats binary pkg for slackware...so dont use it for FC4
http://forum.amule.org/board.php?boardid=69
^^ here is a fedora thread...try this rpm
-
That's a Slackware package.
To get a suitable wxGTK RPM, do the following:
1. Download this file:
http://rpm.pbone.net/index.php3/stat/3/srodzaj/2/search/wxGTK-2.6.2-3.fc5.src.rpm
2. After downloading, run this command:
rpmbuild --rebuild wxGTK-2.6.2-3.fc5.src.rpm
3. Install the resulting RPMs from /usr/src/redhat/RPMS/i?86
This is the RPM that will be part of Fedora Core 5, but with these steps you can also use it on Fedora Core 4.
And it has the side-effect that a patch for a frequently reported wxWidgets bug is already included - you would have to do it manually otherwise.
-
Originally posted by Gerd78
2. After downloading, run this command:
rpmbuild --rebuild wxGTK-2.6.2-3.fc5.src.rpm
This generates a bunch of dependency errors:
sudo rpmbuild --rebuild wxGTK-2.6.2-3.fc5.src.rpm
Installing wxGTK-2.6.2-3.fc5.src.rpm
[...]
error: Failed build dependencies:
libpng-devel is needed by wxGTK-2.6.2-3.i386
libjpeg-devel is needed by wxGTK-2.6.2-3.i386
libtiff-devel is needed by wxGTK-2.6.2-3.i386
expat-devel is needed by wxGTK-2.6.2-3.i386
SDL-devel is needed by wxGTK-2.6.2-3.i386
libgnomeprintui22-devel is needed by wxGTK-2.6.2-3.i386
mesa-libGL-devel is needed by wxGTK-2.6.2-3.i386
mesa-libGLU-devel is needed by wxGTK-2.6.2-3.i386
Sigh.... do I really need to download all these packages?...
I'd much rather just install the rpms that stafanero pointed to above, but http://rapidshare.de/ won't let me download them at the moment ("too many other users") :(
-
Originally posted by Ezeltje
do I really need to download all these packages?...
Yes, wxWidgets needs them to compile.
Or wait until the download of the binary package becomes available again...
-
Stafenero,
Originally posted by stefanero
http://forum.amule.org/board.php?boardid=69
^^ here is a fedora thread...try this rpm
Ok, rapidfile.de let me download those two files this morning, and I installed them the usual way:
$ sudo rpm -ivh wxGTK-2.6.2-1.FC4.i386.rpm aMule-2.1.0-1.FC4.i386.rpm However, I get an error message when I try to start amule now:
$ amule &
[1] 4552
amule: error while loading shared libraries: libwx_gtk_adv-2.6.so.0: cannot open
shared object file: No such file or directory Any idea what is going wrong?
For the time being, I have reverted to wxGTK-2.6.0 and aMule-2.0.2 which were über-stable for me.
-
did you run ldconfig after install? and did you remove teh old wxGTK rpms?
-
Originally posted by stefanero
did you run ldconfig after install?
When I install libraries manually (make install), I run ldconfig, but not after installing RPMs. I thought the package took care of that kind of thing...
and did you remove teh old wxGTK rpms?
Of course. According to locate, libwx_gtk_adv-2.6.so.0 is not on anywhere my system.
That being said, perhaps there is some version mixing going on. When I have a moment, I will try to delete everything and start again from scratch.
However, I am wondering if there is some kind of memory leak problem in 2.1. which is causing it to crash after a few hours. For example, at the start of my last session with 2.1, before reverting to 2.0, amule's virtual memory footprint was ~130m. After six or so hours, however, my system started drastically slowing down; not in CPU activity but disk activity. According to top, amule's memory footprint had grown to 489m. Because amule was no longer responding I had to kill it in a terminal window. Several days previously, I had experience a similar situation; that time, amule's VM footprint had grown in the course of less than 18 hours to a whopping 744m.
I have not seen that kind of problem with 2.0. For example, it has now been running ~20 hours and is using 133MB. I admit I may be a "heavy" user; I am sharing ~1300 files (=571GB) with upload bandwidth of 80kB/s, but 2.0 seems to handle this ok.
If there is anyway I can help you identify the memory problem with 2.1, please let me know.
-
hmm well with I tryed those rpms before, since some other user said this kind of problems...
but here on a fresh installed fc4 they worked without any problems...so I dont really know where those problems come from I doubt its from teh rpms, since they worked here.
about the mem problem. I am not really sharing that many files so it might be likly to have something todo with that, since I dont observe that mem-problems.
a mem-debugger for linux is valgrind, but it will make running amule REALLY SLOW and is only ment for debugging purpose. but if you could provide some usefull infos where amule leaks this would be really appreaciated.
on http://wiki.amule.org there is a valgrind guide, also maybe you can get in touch with Kry or Xaignar, since I dont know exactly what infos are importand from valgrind and what not
thnx for help
stefanero