aMule Bug Tracker - aMule
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001816aMuleMiscpublic2022-04-26 15:442022-04-26 15:44
Reporterraidenii 
Assigned To 
PrioritynormalSeveritycrashReproducibilityalways
StatusnewResolutionopen 
PlatformLinuxOSDebianOS Version11
Product Version2.3.3 
Target VersionFixed in Version 
Fixed in Revision
Operating SystemLinux
Summary0001816: aMuled gets OOM killed over time
DescriptionaMule 2.3.3 keeps leaking memory (albeit at a slow rate) over weeks and eventually get killed by OOM. A similar Github issue was filed by others at https://github.com/amule-project/amule/issues/314. [^]
Steps To Reproduce1. Set up amuled and amuleweb, and start amuled via systemd
2. Wait and see amuled keeps eating ram.
3. OOM and amuled get killed.
Additional InformationaMule logfile suggests that:

Assertion failed: ../../src/kademlia/kademlia/Entry.cpp:ReCalculateTrustValue:463: Assertion '!m_publishingIPs->empty()' failed.
Backtrace follows:
[3] wxOnAssert(char const*, int, char const*, char const*, char const*) in /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f5db6d182d5]
[4] ?? in /usr/bin/amuled[0x564c973eb4ce]
[5] ?? in /usr/bin/amuled[0x564c973eb5c8]
[6] ?? in /usr/bin/amuled[0x564c973f14da]
[7] ?? in /usr/bin/amuled[0x564c973178c6]
[8] ?? in /usr/bin/amuled[0x564c97309378]
[9] ?? in /usr/bin/amuled[0x564c97289453]
[10] ?? in /usr/bin/amuled[0x564c972c9223]
[11] ?? in /usr/bin/amuled[0x564c97288619]
[12] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) in /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f5db6e94241]
[13] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) in /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f5db6e94333]
[14] wxEvtHandler::TryHereOnly(wxEvent&) in /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f5db6e9467c]
[15] wxEvtHandler::ProcessEventLocally(wxEvent&) in /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f5db6e94703]
[16] wxEvtHandler::ProcessEvent(wxEvent&) in /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f5db6e947a1]
[17] wxEvtHandler::ProcessPendingEvents() in /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f5db6e9514e]
[18] wxAppConsoleBase::ProcessPendingEvents() in /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f5db6d1af7f]
[19] wxEventLoopManual::ProcessEvents() in /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f5db6d53b5c]
[20] wxEventLoopManual::DoRun() in /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f5db6d53c2e]
[21] wxEventLoopBase::Run() in /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f5db6d5397d]
[22] wxAppConsoleBase::MainLoop() in /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f5db6d1c9a6]
[23] wxEntry(int&, wchar_t**) in /lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0[0x7f5db6da4a19]
[24] ?? in /usr/bin/amuled[0x564c97243fe2]
[25] __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6[0x7f5db679cd0a]
[26] ?? in /usr/bin/amuled[0x564c9724b81a]

Maybe Kad isn't emptying the list correctly and thus lead to mem leak?
Full logfile attached.
TagsNo tags attached.
Relationships
Attached Filestxt logfile.txt (59,421) 2022-04-26 15:44
https://bugs.amule.org/file_download.php?file_id=382&type=bug
Issue History
Date ModifiedUsernameFieldChange
2022-04-26 15:44raideniiNew Issue
2022-04-26 15:44raideniiFile Added: logfile.txt

There are no notes attached to this issue.