0001248: aMule hogs lots of memory and then dies

(0002541)
Xaignar (manager)
2008-01-26 18:58

Hmm, can you try upgrading to the latest wxWidgets (2.8.7)? Also, yeah, creating a real backtrace is always preferable from our point of view. :)

More information here:
http://www.amule.org/wiki/index.php/Backtraces [^]

Cheers.

(0002542)
JuhaManninen (reporter)
2008-01-26 19:55

I tried to run aMule in gdb to get the real backtrace.
After 3 hours of running it started to hog all memory, including swap, and the machine practically halted. After another hour or 2 the program died with:
"Program terminated with signal SIGKILL, Killed."
"The program no longer exists."

When I tried to get the output from gdb, it said:
"No stack." and
"No registers."

The aMule program was the exact same compilation as earlier.

Juha Manninen

(0002543)
JuhaManninen (reporter)
2008-01-27 00:21

Right!

I compiled wxWidgets 2.8.7 with unicode support, and then compiled aMule again. Now it has been running at least 3 hours without problems. Seems like this solved the case. Thanks for help!

Suse's packages for wxWidgets really should be updated.

Regards,
Juha Manninen

(0002544)
JuhaManninen (reporter)
2008-01-27 01:59

Oops... almost.

The problem is not gone, I was too eager to send a note here.
After 2 more hours the memory usage started to rise again just like before. It ate all memory, also swap, and then finally died with:

Terminated after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
* Could not get symbol names for backtrace

(process:21982): GLib-ERROR (recursed) **: gmem.c:172: failed to allocate 32 bytes
aborting...

-----------------------

Am I really the only person with this problem? At least the other bug reports didn't complain about it. Could it be Suse related? Some other library still?
The new wxWidgets version is now used for sure when compiling.

Juha Manninen

(0002545)
JuhaManninen (reporter)
2008-01-27 11:23

Added a backtrace at "http://forum.amule.org/index.php?topic=14308.0". [^]
Is it helpfull?

Juha Manninen

(0002546)
Xaignar (manager)
2008-01-27 13:01

I'm afraid that the backtrace is not very useful. Please be sure to compile aMule with debugging enabled (--enable-debug) and don't strip the binary, as this makes backtraces much harder to read.

(0002549)
Coronas (reporter)
2008-01-31 08:29

I experience a similar problem with amuled. It will only run for a very short time, sometimes half an hour, sometimes just 5 minutes. After that, the memory consume rises skyhigh, and the app dies. Unfortunately, I can't produce a good backtrace as amuled is running on an embedded device with memory restrictions. Anyway, my workaround was to leave KAD disconnected and work only with the ed2k network. That got definately rid of the problem.

(0002550)
mr_hyde (reporter)
2008-02-02 10:01
edited on: 2008-02-02 10:11

I don't know if my experience can be useful: I hav the problem with amule (never seen with amuled, yes, just the contrary of Coronas), and I observed that amule at beginning works correctly then, (sometimes after some minutes and sometimes after hours), the %CPU value of top command rises near 100% (I have a laptop and I can hear the fan noise) and also the MEM value increases quickly, and at this point PC becomes slow and does not respond to user anymore. Maybe a strange loop? And/or probably I used wrong settings for my network connection? I have fibre connection with 10 Mbit for uploads and 10 Mbit for download, I set 1220 kB/s as download limit, 800 kB/sas upload limit, 40 kB/S for slot allocation and 200 as connection limits, my PC has 2G of RAM.
And just another question: kernel configuration (scheduler and similar settings) may have some influence with amule?

edited on: 02-02-08 10:11

(0002755)
antonovich (reporter)
2008-03-24 17:32

I can confirm that I had this problem with both 2.1.3 on ubuntu 7.10 and now svn on 8.04 beta. It seems to be pretty random but never seems to go more than a day or so now (could last up to 3 or 4 with the stable version). Memory seems to slowly increase (probably with the queue size) and then all of a sudden it will go out of control. I have 6GB of RAM... and when it starts taking 5.8GB it's time for a kill!

(0002883)
Wuischke (manager)
2008-07-21 17:59

Can someone confirm this for current versions? (2.2.1, current SVN)

(0002884)
pcmaster (reporter)
2008-07-22 12:53
edited on: 2008-07-22 12:53

http://www.amule.org/abugs/view.php?id=1359 [^]

It not dies, but it has high memory usage.

edited on: 07-22-08 12:53

(0002908)
Wuischke (manager)
2008-08-13 16:28

I will close this bug report for now as the original problems doesn't seem to exist anymore. The memory problem however seems to be serious.

Notes
(0002541) Xaignar (manager) 2008-01-26 18:58	Hmm, can you try upgrading to the latest wxWidgets (2.8.7)? Also, yeah, creating a real backtrace is always preferable from our point of view. :) More information here: http://www.amule.org/wiki/index.php/Backtraces [^] Cheers.

(0002542) JuhaManninen (reporter) 2008-01-26 19:55	I tried to run aMule in gdb to get the real backtrace. After 3 hours of running it started to hog all memory, including swap, and the machine practically halted. After another hour or 2 the program died with: "Program terminated with signal SIGKILL, Killed." "The program no longer exists." When I tried to get the output from gdb, it said: "No stack." and "No registers." The aMule program was the exact same compilation as earlier. Juha Manninen

(0002543) JuhaManninen (reporter) 2008-01-27 00:21	Right! I compiled wxWidgets 2.8.7 with unicode support, and then compiled aMule again. Now it has been running at least 3 hours without problems. Seems like this solved the case. Thanks for help! Suse's packages for wxWidgets really should be updated. Regards, Juha Manninen

(0002544) JuhaManninen (reporter) 2008-01-27 01:59	Oops... almost. The problem is not gone, I was too eager to send a note here. After 2 more hours the memory usage started to rise again just like before. It ate all memory, also swap, and then finally died with: Terminated after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc * Could not get symbol names for backtrace (process:21982): GLib-ERROR (recursed) **: gmem.c:172: failed to allocate 32 bytes aborting... ----------------------- Am I really the only person with this problem? At least the other bug reports didn't complain about it. Could it be Suse related? Some other library still? The new wxWidgets version is now used for sure when compiling. Juha Manninen

(0002545) JuhaManninen (reporter) 2008-01-27 11:23	Added a backtrace at "http://forum.amule.org/index.php?topic=14308.0". [^] Is it helpfull? Juha Manninen

(0002546) Xaignar (manager) 2008-01-27 13:01	I'm afraid that the backtrace is not very useful. Please be sure to compile aMule with debugging enabled (--enable-debug) and don't strip the binary, as this makes backtraces much harder to read.

(0002549) Coronas (reporter) 2008-01-31 08:29	I experience a similar problem with amuled. It will only run for a very short time, sometimes half an hour, sometimes just 5 minutes. After that, the memory consume rises skyhigh, and the app dies. Unfortunately, I can't produce a good backtrace as amuled is running on an embedded device with memory restrictions. Anyway, my workaround was to leave KAD disconnected and work only with the ed2k network. That got definately rid of the problem.

(0002550) mr_hyde (reporter) 2008-02-02 10:01 edited on: 2008-02-02 10:11	I don't know if my experience can be useful: I hav the problem with amule (never seen with amuled, yes, just the contrary of Coronas), and I observed that amule at beginning works correctly then, (sometimes after some minutes and sometimes after hours), the %CPU value of top command rises near 100% (I have a laptop and I can hear the fan noise) and also the MEM value increases quickly, and at this point PC becomes slow and does not respond to user anymore. Maybe a strange loop? And/or probably I used wrong settings for my network connection? I have fibre connection with 10 Mbit for uploads and 10 Mbit for download, I set 1220 kB/s as download limit, 800 kB/sas upload limit, 40 kB/S for slot allocation and 200 as connection limits, my PC has 2G of RAM. And just another question: kernel configuration (scheduler and similar settings) may have some influence with amule? edited on: 02-02-08 10:11

(0002755) antonovich (reporter) 2008-03-24 17:32	I can confirm that I had this problem with both 2.1.3 on ubuntu 7.10 and now svn on 8.04 beta. It seems to be pretty random but never seems to go more than a day or so now (could last up to 3 or 4 with the stable version). Memory seems to slowly increase (probably with the queue size) and then all of a sudden it will go out of control. I have 6GB of RAM... and when it starts taking 5.8GB it's time for a kill!

(0002883) Wuischke (manager) 2008-07-21 17:59	Can someone confirm this for current versions? (2.2.1, current SVN)

(0002884) pcmaster (reporter) 2008-07-22 12:53 edited on: 2008-07-22 12:53	http://www.amule.org/abugs/view.php?id=1359 [^] It not dies, but it has high memory usage. edited on: 07-22-08 12:53

(0002908) Wuischke (manager) 2008-08-13 16:28	I will close this bug report for now as the original problems doesn't seem to exist anymore. The memory problem however seems to be serious.

Issue History
Date Modified	Username	Field	Change
2008-01-26 15:03	JuhaManninen	New Issue
2008-01-26 15:03	JuhaManninen	Operating System	=> OpenSuse 10.3
2008-01-26 18:58	Xaignar	Note Added: 0002541
2008-01-26 19:55	JuhaManninen	Note Added: 0002542
2008-01-27 00:21	JuhaManninen	Note Added: 0002543
2008-01-27 01:59	JuhaManninen	Note Added: 0002544
2008-01-27 11:23	JuhaManninen	Note Added: 0002545
2008-01-27 13:01	Xaignar	Note Added: 0002546
2008-01-31 08:29	Coronas	Note Added: 0002549
2008-02-02 10:01	mr_hyde	Note Added: 0002550
2008-02-02 10:11	mr_hyde	Note Edited: 0002550
2008-03-24 17:32	antonovich	Note Added: 0002755
2008-03-24 17:32	antonovich	Note Added: 0002756
2008-03-24 17:33	antonovich	Note Added: 0002757
2008-03-24 21:49	Xaignar	Note Deleted: 0002757
2008-03-24 21:49	Xaignar	Note Deleted: 0002756
2008-07-21 17:59	Wuischke	Note Added: 0002883
2008-07-21 17:59	Wuischke	Status	new => feedback
2008-07-22 12:53	pcmaster	Note Added: 0002884
2008-07-22 12:53	pcmaster	Note Edited: 0002884
2008-08-13 16:26	Wuischke	Relationship added	related to 0001359
2008-08-13 16:28	Wuischke	Status	feedback => closed
2008-08-13 16:28	Wuischke	Note Added: 0002908