aMule Forum
English => aMule crashes => Topic started by: tvferret on May 12, 2005, 11:34:04 AM
-
Hi,
Since I am running FC2 I am unable to install rpms for it. I downloaded source for amule 2.0.0 and compiled it myself. I've also installed generic version of wxGTK 2.6 rpms (downloaded from this site). First impresion was good. I've let amule run for whole night and in the morning I can see that it is hanging, i.e. the process seems to be stack in some kind of loop, totally unresponsive, no download, cpu usage at 75%-100%, etc. Main window is still there but completely blank, nothing in the log. Oops, I think, surerly this must be a problem with wxGTK. No time to experiment so I run amuled. Cool, no crashes, no hangs but UI sucks (sorry guys). So I started playing againg with amule. Downloaded wxGTK sources, compiled, installed, ran amule and .... still hangs. I have no idea what this could be. It runs perfectly for few hours and then bang. Next step is to compile debug ver and when it hangs attach to it and see where is stuck. But it takes time and my vocational duties prevent me from spending to much time on this.
Any idea what this might be? I'd really appreciate some help.
Cheers,
Mikey
-
well to be honest I have no clue where the problem is...
without any gdb output or even maybe console msg what happend last its really hard to tell where to problem is
do you use 2.0 source or some version of cvs-tarballs?
stefanero
-
I use standart 2.0.0 source. There is nothing on the console or in the logs (I mean nothing that could be useful). I am going to compile debug version tonite.
-
thnx
-
One more thing, to compile amule I used standard config:
./configure --prefix=/usr --enable-optimize --disable-debug --enable-wxcas --enable-cas --enable-alc --enable-alcc --enable-amule-daemon --enable-amulecmd --enable-amulecmdgui --enable-webserver --enable-webservergui --enable-amule-gui
-
One more question, what does --enable-maintainer-mode do exactly?
-
your configure is fine, alltho I doubt you will use some of those apps you compile but anyways....
about the --enable-maintainer-mode
/me looks for Xaignar or Kry :]
-
Originally posted by stefanero
... I doubt you will use some of those apps you compile but anyways....
You're right, it's just copy and paste from wiki's :D
-
Originally posted by tvferret
One more question, what does --enable-maintainer-mode do exactly?
Please read this:
http://www.gnu.org/software/automake/manual/html_node/maintainer-mode.html
Now that you mention, I think that this option sucks. Kry, what about removing AM_MAINTAINER_MODE from configure.in? It is in the file since aMule initial CVS import.
From the automake docs
Jim Meyering, the inventor of the AM_MAINTAINER_MODE macro was swayed by François's arguments, and got rid of AM_MAINTAINER_MODE in all of his packages.
Cheers!
-
Thanks Phoenix, I am not a Linux guru, most of my professional work is around Solaris and embedded systems running VxWorks for example, so GNU autoconfig is a bit of a mystery for me :D But I'll manage somehow ... I'll try to debug this problem either today or over the weekend and will post results. In the meantime, maybe somebody will have an idea? I strongly suspect wxGTK but will see.
Cheers,
Mikey
PS. Before I upgraded to amule 2.0.0 I was running 2.0.0 RC8, with wxGTK 2.4.2, no problems there, only occasional crash of amule (apparently known problem fixed before 2.0.0 release, as I've read somewhere on this forum).
-
if you have verbose enabled in your prefs, disable it.. it's the most posted "amule kills my CPU" reasons
-
Very quickly, here is a backtrace after attaching with gdb. No bt full because there are no symbols. Have no time to analyze it yet. Gotta go.
(gdb) bt
#0 0x009bd7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x00c162ee in fcntl () from /lib/tls/libpthread.so.0
#2 0x00da4d73 in g_vasprintf () from /usr/lib/libglib-2.0.so.0
#3 0x00da5295 in g_io_channel_unix_new () from /usr/lib/libglib-2.0.so.0
#4 0x0036209f in gdk_input_add_full () from /usr/lib/libgdk-x11-2.0.so.0
#5 0x0036212a in gdk_input_add () from /usr/lib/libgdk-x11-2.0.so.0
#6 0x059c4aac in GSocketGUIFunctionsTableConcrete::Install_Callback () from /usr/lib/libwx_gtk2_core-2.6.so.0
#7 0x002be463 in GSocket::Enable () from /usr/lib/libwx_base_net-2.6.so.0
#8 0x002bdd8c in GSocket::Read () from /usr/lib/libwx_base_net-2.6.so.0
#9 0x002b9bc3 in wxSocketBase::_Read () from /usr/lib/libwx_base_net-2.6.so.0
#10 0x002b9ab5 in wxSocketBase::Read () from /usr/lib/libwx_base_net-2.6.so.0
#11 0x002bb01d in wxDatagramSocket::RecvFrom () from /usr/lib/libwx_base_net-2.6.so.0
#12 0x081c9d57 in CDatagramSocketProxy::RecvFrom ()
#13 0x080a98b3 in CClientUDPSocket::DoReceive ()
#14 0x080a975f in CClientUDPSocket::OnReceive ()
#15 0x0807688f in CamuleGuiApp::ClientUDPSocketHandler ()
#16 0x00424a04 in wxAppConsole::HandleEvent () from /usr/lib/libwx_base-2.6.so.0
#17 0x004bc164 in wxEvtHandler::ProcessEventIfMatches () from /usr/lib/libwx_base-2.6.so.0
#18 0x004bb66d in wxEventHashTable::HandleEvent () from /usr/lib/libwx_base-2.6.so.0
#19 0x004bc2dc in wxEvtHandler::ProcessEvent () from /usr/lib/libwx_base-2.6.so.0
#20 0x004bc0b7 in wxEvtHandler::ProcessPendingEvents () from /usr/lib/libwx_base-2.6.so.0
#21 0x00424985 in wxAppConsole::ProcessPendingEvents () from /usr/lib/libwx_base-2.6.so.0
#22 0x059ab343 in wxapp_pending_callback () from /usr/lib/libwx_gtk2_core-2.6.so.0
#23 0x00d82683 in g_child_watch_add () from /usr/lib/libglib-2.0.so.0
#24 0x00d7f252 in g_main_depth () from /usr/lib/libglib-2.0.so.0
#25 0x00d80348 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0x00d80680 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0x00d80cc3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#28 0x04bf9923 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#29 0x059c2a51 in wxEventLoop::Run () from /usr/lib/libwx_gtk2_core-2.6.so.0
#30 0x05a47eb9 in wxAppBase::MainLoop () from /usr/lib/libwx_gtk2_core-2.6.so.0
#31 0x05a47fdf in wxAppBase::OnRun () from /usr/lib/libwx_gtk2_core-2.6.so.0
#32 0x004618cf in wxEntry () from /usr/lib/libwx_base-2.6.so.0
#33 0x08075f10 in main ()
-
tvferret,
I just answered the part regarding --enable-maintainer-mode :)
Btw, is this a backtrace of when the program is locked? I see nothing wrong there. The only wrong thing is that I see no debug information. Are you sure you used --enable-debug? Maybe you are running another executable of aMule that is first in the path?
Cheers!
-
pheonix,
The backtrace is from the program when it's locked. I attached with gdb, it seems to be stuck in _dl_sysinfo_int80(). Have no idea why though. And I haven't had a chance to compile debug version yet (need to recompile wxGTK as well). Most likely will do it over weekend.
Mikey
-
Hello people
Any news yet about what could be the reason?
I am using Debian Sarge, and i installed amule from an apt-repository i found at apt-get.org, using these sources.list lines:
deb http://www.vollstreckernet.de/debian testing amule
deb http://www.vollstreckernet.de/debian testing wx
deb-src http://www.vollstreckernet.de/debian testing amule
I installed the packages
amule-common_2.0.0-re1+CVS20050511-1_i386.deb
amule_2.0.0-rel+CVS20050511-1_i386.deb
amuleweb_2.0.0-rel+CVS20050511-1_i386.deb
it installed some wx-packages cause of dependencies, dpkg -l *wx* | grep ii shows me the following wx-packages installed:
libwxbase2.4 - Version 2.4.2.6.1
libwxgtk2.4 - Version 2.4.2.6.1
libwxgtk2.5.3 - Version 2.5.3.2-2
I have the same problem as described here, first time i started amule it run fine for about 5 to 7 hours. Then when I came back it was "hanging", cpu-usage was at 100%, amule was consuming most of it.
I killed amule then and restarted it, after about 1 hour it hang again.
In the console I didn't see any messages about a problem, the last lines on the console were things like
Empty dir /somedir
Empty dir /someotherdir
Just thought i'll report it here, so you know you are not the only one with that problem.
If I got some time tomorrow i'll compile wx and the source myself.. but I hoped being able to avoid that.
greetings
Elias
Edit:
I forgot to tell that simply adding the lines
deb http://www.vollstreckernet.de/debian testing amule
deb http://www.vollstreckernet.de/debian testing wx
and doing an
apt-get update
apt-get install amule
(as described at http://www.amule.org/wiki/index.php/HowTo_Compile_In_Debian under Section 'Are you sure you want to compile?')
did not work on my system, I run into an
Package amule is not available, but is reffered to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source.
E: Package amule has no installation candidate
so i just downloaded the packages mentioned above and installed them with dpkg.
-
Hum, ;( I got a lock up here too, with 100% CPU, wtf? :
(gdb) thread apply all bt
Thread 2 (Thread -1210524752 (LWP 10597)):
#0 0x001a07a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x00406be6 in __nanosleep_nocancel () from /lib/tls/libpthread.so.0
#2 0x00636e40 in wxMicroSleep (microseconds=1000) at ./src/unix/utilsunx.cpp:175
#3 0x00636e83 in wxMilliSleep (milliseconds=1) at ./src/unix/utilsunx.cpp:196
#4 0x0062f68c in wxThread::Sleep (milliseconds=1) at ./src/unix/threadpsx.cpp:973
#5 0x0824c27c in UploadBandwidthThrottler::Entry (this=0x8f66968) at UploadBandwidthThrottler.cpp:382
#6 0x0062ee9d in wxThreadInternal::PthreadStart (thread=0x8f66968) at ./src/unix/threadpsx.cpp:763
#7 0x0062ed56 in wxPthreadStart (ptr=0x8f66968) at ./src/unix/threadpsx.cpp:715
#8 0x00401341 in start_thread () from /lib/tls/libpthread.so.0
#9 0x00de8fee in clone () from /lib/tls/libc.so.6
Thread 1 (Thread -1208396096 (LWP 10595)):
#0 0x001a07a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x00ddf404 in poll () from /lib/tls/libc.so.6
#2 0x00ad00a1 in wxapp_poll_func (ufds=0xaaf2f78, nfds=7, timeout=0) at ./src/gtk/app.cpp:363
#3 0x075741d3 in g_main_context_acquire () from /usr/lib/libglib-2.0.so.0
#4 0x075744ef in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#5 0x00f56f97 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#6 0x00aefd67 in wxEventLoop::Run (this=0x99bf658) at ./src/gtk/evtloop.cpp:80
#7 0x00b7f755 in wxAppBase::MainLoop (this=0x8ea0300) at ./src/common/appcmn.cpp:272
#8 0x00b7f8c1 in wxAppBase::OnRun (this=0x8ea0300) at ./src/common/appcmn.cpp:340
#9 0x005d0fdc in wxEntry (argc=@0xbfff06d0, argv=0x8e73568) at ./src/common/init.cpp:417
#10 0x005d111f in wxEntry (argc=@0xbfff06d0, argv=0xbfff0754) at ./src/common/init.cpp:429
#11 0x08082333 in main (argc=1, argv=0xbfff0754) at amule-gui.cpp:297
-
Xaignar,
What about that, is this ok?
Breakpoint 2, UploadBandwidthThrottler::Entry (this=0x8f66968) at UploadBandwidthThrottler.cpp:385
385 const uint32 thisLoopTick = ::GetTickCount();
(gdb) p sleepTime
$1 = 1
(gdb) p timeSinceLastLoop
$2 = 1
(gdb) bt full
#0 UploadBandwidthThrottler::Entry (this=0x8f66968) at UploadBandwidthThrottler.cpp:385
timeSinceLastLoop = 1
minFragSize = 1300
doubleSendSize = 2600
bytesToSpend = 95000
TIME_BETWEEN_UPLOAD_LOOPS = 1
sleepTime = 1
thisLoopTick = 3896979833
realBytesToSpend = 91136999
lastTickReachedBandwidth = 3896978778
lastLoopTick = 3896979833
allowedDataRate = 7168
rememberedSlotCounter = 2
#1 0x0062ee9d in wxThreadInternal::PthreadStart (thread=0x8f66968) at ./src/unix/threadpsx.cpp:763
pthread = (wxThreadInternal *) 0x8f66ad0
rc = 0
dontRunAtAll = false
#2 0x0062ed56 in wxPthreadStart (ptr=0x8f66968) at ./src/unix/threadpsx.cpp:715
No locals.
#3 0x00401341 in start_thread () from /lib/tls/libpthread.so.0
No symbol table info available.
#4 0x00de8fee in clone () from /lib/tls/libc.so.6
No symbol table info available.
(gdb)
-
I'll take a look when I get home. ;)
-
the same thing (or something that has the same characteristics) occurred to me, 15 minutes ago, after ~10 hours of uptime
I've been using amule 2.0.0 since the release, and it never happened before, even with uptime of 24~26 hours
EDIT: it happened again, just now (19:07)
EDIT: again (19:43)
EDIT: again (20:38)
what could it be? amule hangs after less than 20 minutes. maybe a broken client that sends bad packets?
-
ok fixed in 2.0.1 update all ;)
-
I didn't get a chance yet to debug it thoroughly but since it's fixed there is no need to do so :D I'll verify this tonite. But what makes me wonder is that this does not happen (or at least it didn't happen to me) when running daemon (amuled). My impression was that both amule and amuled share the same code. How do you explain that?
-
do you have any idea how long it will take until 2.0.1 is available on volllstreckernet.de as deb-packages?
or are those packages supported by someone you got no contact with?
-
send him a pm or ask in his thread about: http://forum.amule.org/thread.php?threadid=5776&sid=