aMule Forum
English => aMule crashes => Topic started by: stoatwblr on June 18, 2009, 03:48:32 AM
-
Ubuntu 9.04
ZLib operation returned Z_DATA_ERROR
ZLib error message: incorrect data check
zstream state:
next_in=0xbf04e3e
avail_in=0
total_in=56094
next_out=0x91aa5e5b
avail_out=421896125
total_out=73661
[Debug] Generating a stack trace... please wait../../src/ExternalConn.cpp(1538): assert "wxAssertFailure" failed in ProcessRequest2().
Call stack:
[00] 0xb7a0227d
[01] CamuleApp::OnAssertFailure(wchar_t const*, int, wchar_t const*, wchar_t const*, wchar_t const*) /build/buildd/amule-2.3.0~svnr9661/obj-i486-linux-gnu/src/../../src/amule.cpp:1385
[02] wxOnAssert(wchar_t const*, int, char const*, wchar_t const*, wchar_t const*)
[03] CECServerSocket::ProcessRequest2(CECPacket const*, CFileEncoderMap<CPartFile, CPartFile_Encoder, CDownloadQueue>&, CFileEncoderMap<CKnownFile, CKnownFile_Encoder, CSharedFileList>&, CObjTagMap&) /build/buildd/amule-2.3.0~svnr9661/obj-i486-linux-gnu/src/../../src/ExternalConn.cpp:1539
[04] CECServerSocket::OnPacketReceived(CECPacket const*) /build/buildd/amule-2.3.0~svnr9661/obj-i486-linux-gnu/src/../../src/ExternalConn.cpp:140
[05] CECSocket::OnInput() /build/buildd/amule-2.3.0~svnr9661/obj-i486-linux-gnu/src/libs/ec/cpp/../../../../../src/libs/ec/cpp/ECSocket.cpp:439
[06] CECMuleSocketHandler::SocketHandler(wxSocketEvent&) /build/buildd/amule-2.3.0~svnr9661/obj-i486-linux-gnu/src/libs/ec/cpp/../../../../../src/libs/ec/cpp/ECMuleSocket.cpp:58
[07] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) const
[08] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[09] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[10] wxEvtHandler::ProcessEvent(wxEvent&)
[11] wxEvtHandler::ProcessPendingEvents()
[12] wxAppConsole::ProcessPendingEvents()
[13] CamuleDaemonApp::OnRun() /build/buildd/amule-2.3.0~svnr9661/obj-i486-linux-gnu/src/../../src/amuled.cpp:662
Trace/breakpoint trap
-
That's an EC error. What did you connect to what, and which one asserted?
(And I think the zlib message might be unrelated.)
-
Amulegui to amuled and it was amuled which asserted.
Amulegui has been asserting too, but I'm not runnnig it in a terminal.
Why use Zlib on a localhost connection? This will merely slow things down.
(Ditto on any network faster than 10Mb/s ethernet)
-
Both from the same SVN version?
-
yes, both 9661. I always update both in sync out of Festor's Ubuntu builds.
As a side note, configuration options allows selectable compression to amuleweb but not to ECs.
As a general rule in client-server stuff, the server should be set to allow it if requested, but selection of compression/nocompression should be a client-side option. This allows localhost/LAN/WAN/Internet connectors to pick which suits them best - compression gives speed, cpu and memory penalties on fast links or links which are already using some form of compression (some of $orkplace's high end networking gear has hardware compression engines for P-T-P WAN links that's good up to 1Gb/s as a f'instance) and can be pretty counterproductive on CPU-bound machines.
If you want to get really funky, some form of handshake testing if there's any speed penalty for compression would allow selectionto be done automagically.
Something like that would need an override option though, along the lines of "compresion = auto/on/off" for edge cases.
-
Amulegui has been asserting too, but I'm not runnnig it in a terminal.
Amulegui is always asserting when you shut down the server. :P
Have you got this more than once?