aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: amule 2.3.2 with wxWidgets 3.0 eats up all RAM  (Read 603 times)

evaristo

  • Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 2
amule 2.3.2 with wxWidgets 3.0 eats up all RAM
« on: February 27, 2017, 07:43:13 PM »

I use Packman's amule package in my openSUSE Tumbleweed and Leap 42.2 machines (both x86_64) and with the last two updates amule always starts to eat up all available RAM until the kernel kills it. It uses wxWidgets 3.0 (I have installed 3.0.2 version)

It seems to occur when a message like "(amule:4890): GLib-CRITICAL **: Source ID 506 was not found when attempting to remove it" shows in the console when starting the application from command line (numbers in parenthesis change).

I downloaded amule 2.3.2 from SourceForge and compiled it successfully with the next options (enabled debugging):

./configure --enable-geoip --enable-wxcas --enable-amule-gui --enable-amulecmd --enable-alc --enable-alcc --enable-cas --enable-debug --enable-ccache --enable-mmap --enable-static-boost --enable-xas --enable-maintainer-mode --prefix=$HOME/Descargas/aMule/aMule-test

When I launch $HOME/Descargas/aMule/aMule-test/bin/amule the same thing happens.

I tried to debug using the guide http://wiki.amule.org/wiki/Backtraces and if I wait until the kernel kills amule and do the bt commands nothing shows, so I had to Ctrl+C when first error message shows up to get a backtrace (http://forum.amule.org/index.php?topic=21639.msg110967)

I hope anyone can provide any clue on what to check to solve the problem.

Thanks in advance
« Last Edit: February 27, 2017, 08:06:46 PM by evaristo »
Logged