[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Mldonkey-bugs] [bugs #8716] one cpu spikes to 99% after 10 hours.

From: anonymous
Subject: [Mldonkey-bugs] [bugs #8716] one cpu spikes to 99% after 10 hours.
Date: Wed, 28 Apr 2004 00:28:46 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

This mail is an automated notification from the bugs tracker
 of the project: mldonkey, a multi-networks file-sharing client.

[bugs #8716] Full Item Snapshot:

URL: <>
Project: mldonkey, a multi-networks file-sharing client
Submitted by: 0
On: Wed 04/28/04 at 00:28

Category:  Core
Severity:  5 - Average
Item Group:  Compilation problem
Resolution:  None
Assigned to:  None
Status:  Open
Release:  2.5.18
Release:  started in 2.5.12
Platform Version:  Linux
Binaries Origin:  Downloaded from third-party page
CPU type:  Intel x86

Summary:  one cpu spikes to 99% after 10 hours.

Original Submission:  dual P2 266 machine with 256MB ram.

I started having this problem around 2.5.12.  i have tried SpiralVoice's cores 
as well as building my own cvs cores.  all give the same results.  this last 
time i used the 2.5-18 core from Spiralvoice's page and I had disabled all 
networks except eDonkey some 7 hours before it crashed.

everything seems to run fine and downloads are fast, but after about 10 hours 
of running, mlnet cpu useage will spike to 99% and i can no longer log into the 
core.  I have to kill-9 it. 

i have made the buginfo and included the logfile in the archive 
(mld.log.crash).  i can get more info if required and i'm more than happy to 
help any way i can.

I've toyed with various options settings, but, like i said, everything else 
seems to be fine (mem useage, etc...).  and i have trouble figureing out 
exactly when it's going to crash.

File Attachments

Date: Wed 04/28/04 at 00:28  Name: buginfo.tar.gz  Size: 244KB   By: None
buginfo + logfile;item_file_id=1244

For detailed info, follow this link:

  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]