Remove this ad

Lead

Dec 15 13 3:14 PM

Tags : :

Thsi happened whilst I was deleting some queued downloads at the same time as a reload shared was being run.

----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMuleD SVN compiled with wxGTK2 v2.8.12 and Boost 1.53 (Debugging) (Snapshot: rev. 10814)
Running on: Linux 3.11.0-3-generic x86_64

[2] wxFatalSignalHandler in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f5306f396cc]
[3] CFileAreaSigHandler::Handler(int, siginfo_t*, void*) in FileArea.cpp:120
[4] ?? in /lib/x86_64-linux-gnu/libpthread.so.0[0x7f5306430bb0]
[5] ?? in /lib/x86_64-linux-gnu/libc.so.6[0x7f53061a2d9c]
[6] wxStringBase::wxStringBase(wchar_t const*, unsigned long) in string.h:370
[7] wxString::wxString(wchar_t const*, unsigned long) in string.h:701
[8] DeepCopy(wxString const&) in Path.cpp:79
[9] CPath:perator=(CPath const&) in Path.cpp:322
[10] CFile::Open(CPath const&, CFile::OpenMode, int) in CFile.cpp:236
[11] CFileAutoClose::Open(CPath const&, CFile::OpenMode) in FileAutoClose.cpp:54
[12] CPartFile::AllocationFinished() in PartFile.cpp:4014
[13] CamuleApp::OnFinishedAllocation(CAllocFinishedEvent&) in amule.cpp:1351
[14] wxEvtHandler:rocessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f5306f36756]
[15] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f5306f367fb]
[16] wxEvtHandler:rocessEvent(wxEvent&) in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f5306f36b67]
[17] wxEvtHandler:rocessPendingEvents() in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f5306f366b8]
[18] wxAppConsole:rocessPendingEvents() in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f5306eb41b1]
[19] CamuleDaemonApp::OnRun() in amuled.cpp:623
[20] wxEntry(int&, wchar_t**) in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f5306ee3e2d]
[21] main in amuled.cpp:122
[22] __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6[0x7f530607ade5]
[23] ?? in amuled[0x42d989]

--------------------------------------------------------------------------------
Quote    Reply   
Remove this ad
Remove this ad

#1 [url]

Dec 15 13 8:55 PM

Re: oops

I think you started some downloads and then deleted them again quickly.
You have the preallocate option checked, so aMule allocates them to full size in the background. Before this task finishes you delete them again and aMule crashes on access of already deleted data.

Reload shared probably keeps the background task busy long enough so you have time to delete the files before allocation finishes (or probably even starts).

I'll look into it. Thanks for reporting!

Quote    Reply   
Add Reply

Quick Reply

bbcode help