I've always found amule a bit unrealiable (as in it crashes and disappears), but it much more likely to crash if I add lots of files with lots of available sources. Presumably this is because whatever causes the crashes is much more likely to happen if there are more sources / files involved.
I'm running Fedora 10 64bit. I will add below backtaces as they happen to see if it is always the same error.
1st crash 15:40 Sun 14th December
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule 2.2.2 using wxGTK2 v2.8.9
Running on: Linux 2.6.27.7-134.fc10.x86_64 x86_64
[2] wxString::~wxString() in amule [0x44658f]
[3] wxFatalSignalHandler in /usr/lib64/libwx_baseu-2.8.so.0[0x3d9faf9ffc]
[4] ?? in /lib64/libpthread.so.0 [0x3f1660f0f0]
[5] wxColour::wxColour(unsigned char, unsigned char, unsigned char, unsigned char) in amule [0x56d100]
[6] wxDataObjectSimple::~wxDataObjectSimple() in amule [0x518428]
[7] wxDataObjectSimple::~wxDataObjectSimple() in amule [0x518afe]
[8] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) in /usr/lib64/libwx_baseu-2.8.so.0[0x3d9faf5969]
[9] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) in /usr/lib64/libwx_baseu-2.8.so.0[0x3d9faf6b44]
[10] wxEvtHandler::ProcessEvent(wxEvent&) in /usr/lib64/libwx_baseu-2.8.so.0[0x3d9faf6c37]
[11] wxTimerBase::Notify() in /usr/lib64/libwx_gtk2u_core-2.8.so.0[0x3b7eee8e86]
[12] ?? in /usr/lib64/libwx_gtk2u_core-2.8.so.0 [0x3b7edeee1b]
[13] ?? in /lib64/libglib-2.0.so.0 [0x3392637f5b]
[14] g_main_context_dispatch in /lib64/libglib-2.0.so.0[0x339263779b]
[15] ?? in /lib64/libglib-2.0.so.0 [0x339263af6d]
[16] g_main_loop_run in /lib64/libglib-2.0.so.0[0x339263b49d]
[17] gtk_main in /usr/lib64/libgtk-x11-2.0.so.0[0x3b7df233c7]
[18] wxEventLoop::Run() in /usr/lib64/libwx_gtk2u_core-2.8.so.0[0x3b7ede6768]
[19] wxAppBase::MainLoop() in /usr/lib64/libwx_gtk2u_core-2.8.so.0[0x3b7ee6fafb]
[20] wxEntry(int&, wchar_t**) in /usr/lib64/libwx_baseu-2.8.so.0[0x3d9fa99b8d]
[21] std::basic_string<char, std::char_traits<char>, std::allocator<char> > std::operator+<char, std::char_traits<char>, std::allocator<char> >(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) in amule [0x5136f2]
[22] __libc_start_main in /lib64/libc.so.6[0x3f15e1e546]
[23] ?? in amule [0x445599]
One thing I would really like to suggest is a notification (dialog box would do) whenever there is a fatal crash. It would make it easier to spot something has gone wrong, rather than have to keep checking amule is still going.
