0000142: Crashes if bw limit set to high

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000142

aMule

Misc

public

2004-09-23 05:46

2004-10-19 20:09

Reporter

jkohen

Assigned To

Priority

normal

Severity

crash

Reproducibility

always

Status

closed

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0000142: Crashes if bw limit set to high

Description

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.

Additional Information

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.

Tags

No tags attached.

Fixed in Revision

Operating System

Attached Files

Relationships

Notes
(0000272) Xaignar (manager) 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 (reporter) 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 (manager) 2004-09-25 22:36	Ok, thanks anyway, I'll try to see if I can figoure out what caused it.

(0000310) Kry (manager) 2004-10-19 20:09	No way to reproduce, closing it for now :)

Issue History
Date Modified	Username	Field	Change
2004-09-23 05:46	jkohen	New Issue
2004-09-23 15:04	Xaignar	Note Added: 0000272
2004-09-24 13:25	jkohen	Note Added: 0000275
2004-09-25 22:36	Xaignar	Note Added: 0000279
2004-10-19 20:09	Kry	Note Added: 0000310
2004-10-19 20:09	Kry	Status	new => closed