aMule Forum
English => aMule crashes => Topic started by: Alzii on January 14, 2005, 05:58:11 PM
-
ok i got a really strange bug/error/??
first:
I moved the temp-files & the clients.met & servers.met from another pc (amule rc7) to my server.
there i installed amule 2.0.0rc8 and put the clients.met & servers.met into the ./amule directory.
Then i started amule and changed the path for the temp files to my till now downloaded tempfiles. --> restart --> he starts up tries to connect to a server but seems like some of the part.met files of the temp dir are broken ... so he tried to hash these files ...
after about 20 mins hashing for about 12 files he stops hashing with:
Hasher: No files on queue, stopping thread.
Hasher: A thread has died.
After that amule doesn't do anything than eating cpu-power.
Anyone any idea why this is ?
Thanks for the answers
Alzii
OS: Debian
amule: 2.0.0rc8
wxGTK2 v2.5.3
-
hi,
do you have verbose enabled in your preferences?
-
after removing some stuff (tempfiles/.....) amule just crashes with this error:
-------------------------------------------------------------------------------
OOPS! Houston, we have a situation: seems like aMule crashed!
Please, post these lines on the backtrace forum on http://www.amule.org/
aMule version is: 2.0.0rc8 using wxGTK2 v2.5.3 (Unicoded)
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
- CamuleApp::OnFatalException() in amule[0x827c063]
[1] wxFatalSignalHandler in /usr/lib/libwx_baseu-2.5.so.3
[0x406965e8]
[2] ?? in /lib/libpthread.so.0 [0x40030825]
[3] ?? in /lib/libc.so.6 [0x40e355e8]
[4] wxString::Cmp(wxString const&) const in /usr/lib/libwx_baseu-2.5.so.3[0x4064cef6]
[5] CServerListCtrl::SortProc(long, long, long) in amule[0x822df0d]
[6] CMuleListCtrl::GetInsertPos(long) in amule[0x817f873]
[7] CServerListCtrl::RefreshServer(CServer*) in amule[0x822b3d9]
[8] CServerListCtrl::AddServer(CServer*) in amule[0x822a86b]
[9] CamuleGuiApp::NotifyEvent(GUIEvent) in amule[0x8280ced]
[10] CamuleApp::AddServer(CServer*) in amule[0x827eaa5]
[11] CServerSocket::ProcessPacket(char const*, unsigned, unsigned char) in amule[0x82304f2]
[12] CServerSocket::PacketReceived(Packet*) in amule[0x8233703]
[13] CEMSocket::OnReceive(int) in amule[0x80e4374]
[14] CServerSocket::OnReceive(wxSocketError) in amule[0x822eea0]
[15] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) const in /usr/lib/libwx_baseu-2.5.so.3[0x405e2d78]
[16] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) in /usr/lib/libwx_baseu-2.5.so.3[0x40690850]
[17] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) in /usr/lib/libwx_baseu-2.5.so.3[0x4068fccf]
[18] wxEvtHandler::ProcessEvent(wxEvent&) in /usr/lib/libwx_baseu-2.5.so.3[0x406909f0]
[19] wxEvtHandler::ProcessPendingEvents() in /usr/lib/libwx_baseu-2.5.so.3[0x40690786]
[20] wxAppConsole::ProcessPendingEvents() in /usr/lib/libwx_baseu-2.5.so.3[0x405e2ce6]
[21] ?? in /usr/lib/libwx_gtk2u_core-2.5.so.3 [0x40320735]
[22] ?? in /usr/lib/libglib-2.0.so.0 [0x40cce033]
[23] ?? in /usr/lib/libglib-2.0.so.0 [0x40ccac02]
[24] g_main_context_dispatch in /usr/lib/libglib-2.0.so.0[0x40ccbcf8]
[25] ?? in /usr/lib/libglib-2.0.so.0 [0x40ccc030]
[26] g_main_loop_run in /usr/lib/libglib-2.0.so.0[0x40ccc673]
[27] gtk_main in /usr/lib/libgtk-x11-2.0.so.0[0x409bcc83]
[28] wxEventLoop::Run() in /usr/lib/libwx_gtk2u_core-2.5.so.3[0x4033b208]
[29] wxAppBase::MainLoop() in /usr/lib/libwx_gtk2u_core-2.5.so.3[0x403cc233]
[30] wxAppBase::OnRun() in /usr/lib/libwx_gtk2u_core-2.5.so.3[0x403cc39a]
[31] wxEntry(int&, wchar_t**) in /usr/lib/libwx_baseu-2.5.so.3[0x40626a63]
[32] wxEntry(int&, char**) in /usr/lib/libwx_baseu-2.5.so.3[0x40626b3d]
[33] main in amule[0x827ff0b]
[34] __libc_start_main in /lib/libc.so.6[0x40e21dc6]
[35] wxMemoryDC::SetPen(wxPen const&) in amule[0x80cfaa1]
--------------------------------------------------------------------------------
Abgebrochen
-
hmm after some more testing it seems that it has to do something with the 'connect on startup'-option cause:
on --> crash after startup
off --> no crash even if i manually select a server and connect
-
ok now i found another error/ ?bug?: (therefor i changed the topic)
i start amuleweb ... all works fine (if i do it like descripted above) but therefor this happens:
(amuleweb)
ECSocket::ReadBuffer error The socket is non-blocking and the operation would block
Speicherzugriffsfehler
every time i try to add a ed2k-link via webfrontend on another pc (browser: firefox, gentoo)
afterwards i have to restart amuleweb
any idea on this?
thanks for the answers :)
Alzii
-
ok...crashes here aswell
wrote a note to teh amule-web devel
thnx
stefanero
-
seems like i found another bug:
if u keep logged in into the webinterface for several hours it just crashes with:
Speicherzugriffsfehler
if u log out every time after browsing through the webpage it won't crash :)
-
Speicherzugriffsfehler
Can you pleas translate this to english ?
-
mem access error
-
lol, that's one long word!
-
heh in germany you can put many words "together" and make one word out of it ;)