aMule Bug Tracker - aMule
View Issue Details
0000142aMuleMiscpublic2004-09-23 05:462004-10-19 20:09
jkohen 
 
normalcrashalways
closedopen 
 
 
0000142: Crashes if bw limit set to high
I set my UL/DL limits too high, accidentaly. I actually set them to be 8 times the real ones (bits... bytes). The thing is that amule was crashing every few minutes, even just seconds some times. This noon (12 hours ago) I found out about my mistake and fixed the values. AMule hasn't crashed a single time since then, and my usage patterns haven't changed at all.

The hard limits were set to 3072kB/256kB and the soft at about 80% of the former. I could do anything with the "crashing setup," transfer, search, add/remove files from the list, hash, rehash, connect/disconnect from servers, etc. Only that not for too long before I had to restart the software.
I'm using aMule from Debian unstable, namely amule-1.2.6+rc5-2.1 (don't let the name fool you, it's actually 2.0-rc5). I'm running Linux 2.6.8.1 on a i386 CPU.

No backtraces are being dumped when aMule crashes this way.
No tags attached.
Issue History
2004-09-23 05:46jkohenNew Issue
2004-09-23 15:04XaignarNote Added: 0000272
2004-09-24 13:25jkohenNote Added: 0000275
2004-09-25 22:36XaignarNote Added: 0000279
2004-10-19 20:09KryNote Added: 0000310
2004-10-19 20:09KryStatusnew => closed

Notes
(0000272)
Xaignar   
2004-09-23 15:04   
Could you try creating a backtrace using the procedure found at this url?
http://www.amule.org/wiki/index.php/Backtraces [^]

Cheers,
 Xaignar
(0000275)
jkohen   
2004-09-24 13:25   
UHm... weird. I tried to reproduce it again, but wasn't able to. This is annoying, as aMule crashed dozens of times before I changed the speed limits to reasonable settings. I don't think I changed anything else.
(0000279)
Xaignar   
2004-09-25 22:36   
Ok, thanks anyway, I'll try to see if I can figoure out what caused it.
(0000310)
Kry   
2004-10-19 20:09   
No way to reproduce, closing it for now :)