amule crashes when trying to download kad nodes

Please, can you attach backtrace/crash dump. I was not able to reproduce this on my edgy.

Actually amule rather silently closes than crashes. Is there a location I can look for a crash dump or force amule to produce one?

Thanks for reply, Here is a good tutorial how to get backtraces
https://wiki.ubuntu.com/Backtrace

Here you are. Amule behaves slightly different while running unter gdb - it segfaults but keeps the window open. But you see the segfault in the attached log. Hope that helps.

Thank you, this is confirmed.

Reported to upstream: http://www.amule.org/abugs/view.php?id=1007

Confirmed here with Feisty up-to-date and amule 2.1.3-1ubuntu1.

ville palo, could you see the status of the upstream report?

Thanks
Pochu

Probably a bug in wxwidgets

No problem with wxwidgets 2.8.0 and amule cvs (20070131).

We should wait to have this fixed :)

Tried again with amule cvs and wxgtk cvs, and still happens :(

I am having this behavior on feisty (beta), it seems to happen when amule is unable to get the kad nodes list (it gives a 404 now).

Both amule and wxwidets have recently been updated in gutsy. Does this behaviour still apply to the current development environment? Please test with amule 2.1.3-2ubuntu1 (or higher) and wxwidgets 2.8.3.0-0ubuntu1 (or higher). Thank you.

Emmet,

It still happens here (Gutsy up-to-date).

I've downloaded the nodes several times in a few seconds, and I get the crash.

Thank you for retesting.

tHe bUgZorZ suX0rZ..!

Amules been crashing on me ever since breezy.. Update node,, Krash BOOM.. CRAP!! and I'm like WTF? Whreez my ProNZ!!

Same problem here, when i click the button tu update the server list, it shows the screen with the rabbit and in 5 seconds it crashes. I am running kubuntu feisty 2.6.20-16-generic

I'm sorry, if I post this message to incorrect topic.

I have aMule crashed when clicking "Preferences".

It seems, it also can be connected to "wxwidgets2.8 (Ubuntu)", but may be a separate problem.

Just to confirm: those of you, who get aMule crashed when clicking "download kad nodes", do you get it crashed also when clicking "Preferences"?

I.e., should I wait for _this_ bug's resolution, or, it would be better to submit another issue?

Thank you in advance.

PS: Ubuntu Feisty Fawn 7.04; Theme: Clearlooks; WM: Compiz.

I Have the same problem. When amule try to download the kad server list, it crash.

~$ uname -a
Linux netstar 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux

~$ cat /etc/issue
Ubuntu 7.10 \n \l

~$ amule
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /home/diego/.aMule/Temp.

All PartFiles Loaded.
ListenSocket: Ok.

External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Empty dir /home/diego/.aMule/Incoming/ shared
HTTP download thread started

--------------------------------------------------------------------------------
A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
    http://forum.amule.org/board.php?boardid=67
If possible, please try to generate a real backtrace of this crash:
    http://www.amule.org/wiki/index.php/Backtraces

----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule 2.1.3 using wxGTK2 v2.8.4 (Unicoded)
Running on: Linux 2.6.22-14-generic x86_64

[2] wxThreadHelperThread::~wxThreadHelperThread() in amule [0x445575]
[3] wxFatalSignalHandler in /usr/lib/libwx_baseu-2.8.so.0[0x2b246fc8f64c]
[4] ?? in /lib/libpthread.so.0 [0x2b246e523100]
[5] wxGIFDecoder::GetFrameSize(unsigned int) const in /usr/lib/libwx_gtk2u_core-2.8.so.0[0x2b246f5cdfba]
[6] wxGIFDecoder::ConvertToImage(unsigned int, wxImage*) const in /usr/lib/libwx_gtk2u_core-2.8.so.0[0x2b246f5ce01c]
[7] wxTextCtrl::wxTextCtrl() in amule [0x5e4056]
[8] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) in /usr/lib/libwx_baseu-2.8.so.0[0x2b246fc8b66f]
[9] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) in /usr/lib/libwx_baseu-2.8.so.0[0x2b246fc8b80f]
[10] wxEvtHandler::ProcessEvent(wxEvent&) in /usr/lib/libwx_baseu-2.8.so.0[0x2b246fc8b959]
[11] wxTimerBase::Notify() in /usr/lib/libwx_gtk2u_core-2.8.so.0[0x2b246f612d76]
[12] ?? in /usr/lib/libwx_gtk2u_core-2.8.so.0 [0x2b246f509a14]
[13] ?? in /usr/lib/libglib-2.0.so.0 [0x2b2471f2d70b]
[14] g_main_context_dispatch in /usr/lib/libglib-2.0.so.0[0x2b2471f2cfd3]
[15] ?? in /usr/lib/libglib-2.0.so.0 [0x2b2471f302dd]
[16] g_main_loop_run in /usr/lib/libglib-2.0.so.0[0x2b2471f305ea]
[17] gtk_main in /usr/lib/libgtk-x11-2.0.so.0[0x2b247252c883]
[18] wxEventLoop::Run() in /usr/lib/libwx_gtk2u_core-2.8.so.0[0x2b246f50150d]
[19] wxAppBase::MainLoop() in /usr/lib/libwx_gtk2u_core-2.8.so.0[0x2b246f592c8b]
[20] wxEntry(int&, wchar_t**) in /usr/lib/libwx_baseu-2.8.so.0[0x2b246fc2a80c]
[21] CryptoPP::IteratedHash<unsigned int, CryptoPP::EnumToType<CryptoPP::ByteOrder, 0>, 64u, CryptoPP::HashTransformation>::~IteratedHash() in amule [0x4e66a2]
[22] __libc_start_main in /lib/libc.so.6[0x2b24706b9b44]
[23] CryptoPP::BufferedTransformation::ChannelPut2(std::string const&, unsigned char const*, ...

Me, the same bug as D!ego's above.

There's a fix out there, but I'd much rather use a supported update than a CVS build.

aMule 2.2.0 is freeze, waiting for some bug fixes after it's released. Hopefully we will get it in the archive soon (as soon as it's released).

I really hope I don't come off as rude here, but I get frustrated and tweak out...
umm....Why is this not fixed/backported/reverted?
It worked on my last installation, and the one before(etc. to half way through feisty) but...not now.
Why did this package get 'updated' when it just breaks an installation? is this a sporadic problem, with no current known cause?
Again, the current version out there fixes this problem, but for some reason there's not even a patch? I'd like to help somehow, but I don't even know where to start, and I'm not much help when I'm this frustrated. I have 30+gb worth of unfinished downloads just taking up space.

To sum up, it used to work, now it doesn't, there's a fix, it's not available through apt, I want to help, I don't know how, and doubt I'd do that well at it.

Pulling out his own hair,

G.Z.

TheGZeus wrote:
> I really hope I don't come off as rude here, but I get frustrated and tweak out...
> umm....Why is this not fixed/backported/reverted?

Could you please tell us what's exactly broken? If you are referring to exactly
this bug (amule crashing when downloading kad nodes) it has never worked fine
for me, e.g. if I click on the button more than once very quickly amule will
crash. (I forwarded that upstream but amule devs said it was wxWidgets fault and
vice versa).

> It worked on my last installation, and the one before(etc. to half way through feisty) but...not now.
> Why did this package get 'updated' when it just breaks an installation? is this a sporadic problem, with no current known cause?

It works fine to me (except some corner cases as clicking 3 or 4 times in the
kad nodes or the serverlist) so could you please say what's broken? Is it that
the amule doesn't upgrade cleanly (and if so from which release to which one)?
Or that it doesn't start? Or that it crashes when doing something (and doing what)?

> Again, the current version out there fixes this problem, but for some reason there's not even a patch? I'd like to help somehow, but I don't even know where to start, and I'm not much help when I'm this frustrated. I have 30+gb worth of unfinished downloads just taking up space.

Which version? Do you mean upstream's CVS tarball? If so, a) we do not have it
yet since it's not final (although we may include it if it's not final for
Hardy) and b) I tried it yesterday and I could reproduce this bug (the kad
nodes). So what package are you talking about?

>
> To sum up, it used to work, now it doesn't, there's a fix, it's not
> available through apt, I want to help, I don't know how, and doubt I'd
> do that well at it.

An start would be specifying which fix is out there :) Then we could get it in.

Cheers,
Emilio

>
> Pulling out his own hair,
>
> G.Z.
>

Thanks for replying!
Knowing that it's being looked into is a great re-assurance.

I cannot update even once(one click crashes), and thus cannot connect.
If there have been no changes since the intro of Gutsy, then it's probably a very strange little bug that works/breaks on different (base OS) installations for no reason I can see... I have encountered that on other programs (again, no idea why) and gotten them to work after re-installing the OS.
The reason I assumed it had been updated and broken is I never had this problem before my most recent installations of Xubuntu/Kubuntu.

I wish there was less finger-pointing and more problem solving out there. I wish I could be part of the solution... Well, I'm going to start studying programming so....

amule forum have a thread about this problem and solution (ubuntu's packs with fixed version, apparently)

http://forum.amule.org/index.php?topic=13700.0

AFAICS this is really not a wxWidgets bug (as I tried to explain at the linked SF bug report, it could be a bug in wx but nothing in the provided backtrace indicates it). The fact that there are apparently patches to aMule fixing it also seem to show that the problem is in aMule (and was fixed there besides) and not in wx, so I believe this bug "package" field should be changed and that it should be closed when the new aMule version becomes available in Ubuntu.

Reassigning to amule based on patch being available for amule without apparent corresponding wxwidgets changes

This is fixed here on Hardy using the latest wxwidgets 2.8.7.1 and amule 2.2.0~svn20080218.

Could someone confirm it?

I don't know whether I'll be able to get a patch for Gutsy for this, as wxwidgets' developers say this is aMule's fault, and vice versa:
http://forum.amule.org/index.php?topic=12525.0
http://sourceforge.net/support/tracker.php?aid=1707409