aMule Forum

English => aMule crashes => Topic started by: baaba on May 14, 2008, 10:34:31 PM

Title: aMule 2.1.3 crash
Post by: baaba on May 14, 2008, 10:34:31 PM

Hi, ALL! I had any problems with Amule :-\
I am already using Amule with ports of my distributive Linux, but now I can`t start program.
I am using CRUX 2.4
Thanks,
Ivan, Moscow

$ uname -a
Linux Panama 2.6.23.14 #1 SMP Sun May 11 15:37:37 MSD 2008 i686 pentium4 i386 GNU/Linux

$ amule -v
aMule 2.1.3 using wxGTK2 v2.6.4 (OS: Linux)

$ amule --sync
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
The program 'amule' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 1202 error_code 11 request_code 145 minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Title: Re: aMule 2.1.3 crash
Post by: Stu Redman on May 15, 2008, 09:54:31 PM

Welcome to the forum!

2.1.3 is now seriously outdated. Please try a current SVN snapshot.