mldonkey-bugs
[Top][All Lists]
Advanced

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

[Mldonkey-bugs] [bugs #8187] mldonkey is now a memory hog


From: anonymous
Subject: [Mldonkey-bugs] [bugs #8187] mldonkey is now a memory hog
Date: Mon, 04 Oct 2004 17:30:18 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040614 Firefox/0.9

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

/**************************************************************************/
[bugs #8187] Latest Modifications:

Changes by: Anonymous user
Date:  
                Mon 10/04/2004 at 17:22

------------------ Additional Follow-up Comments ----------------------------
mldonkey IS leaking all over the place. I have tested with 2.5.28 and 2.5.22 on 
UltraSparc with 2.4.27. i386 with 2.4.27 and 2.6.8.1. and ocaml 3.07-r1 and 
3.08.1.

I have the same problem all memory is claimed and not released when the core3 
is killed. I haven't ran the gui on either of the machines... I will sit down 
and see if I can find the leak, but don't hold your breath. I normally code on 
Windows.

What version of ocaml are the people who dont have memleaks running?

PS. Only donkey and overnet enabled.






/**************************************************************************/
[bugs #8187] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=8187>
Project: mldonkey, a multi-networks file-sharing client
Submitted by: 0
On: Thu 03/18/2004 at 05:03

Category:  None
Severity:  5 - Average
Item Group:  Memory leak
Resolution:  Duplicate
Privacy:  Public
Assigned to:  None
Status:  Closed
Release:  2-5-16
Release:  
Platform Version:  Linux
Binaries Origin:  CVS / Self compiled
CPU type:  None


Summary:  mldonkey is now a memory hog

Original Submission:  I used to have mldonkey running in a box with 64MB, and 
had no problems even with thousands of sources.  But since the last releases, 
the memory usage of mldonkey grows beyond bounds.

Right now its sucking 90% of a 512 MB box with less than 1000 sources and 3 
days of uptime, and therefore I suspect a memory leak.

Follow-up Comments
------------------


-------------------------------------------------------
Date: Mon 10/04/2004 at 17:22       By: 0 <None>
mldonkey IS leaking all over the place. I have tested with 2.5.28 and 2.5.22 on 
UltraSparc with 2.4.27. i386 with 2.4.27 and 2.6.8.1. and ocaml 3.07-r1 and 
3.08.1.

I have the same problem all memory is claimed and not released when the core3 
is killed. I haven't ran the gui on either of the machines... I will sit down 
and see if I can find the leak, but don't hold your breath. I normally code on 
Windows.

What version of ocaml are the people who dont have memleaks running?

PS. Only donkey and overnet enabled.

-------------------------------------------------------
Date: Thu 07/22/2004 at 20:13       By: spiralvoice <spiralvoice>
Some networks (i.e. Gnutella) have known memory leaks, here RAM usage is stable.

-------------------------------------------------------
Date: Tue 05/04/2004 at 15:05       By: spiralvoice <spiralvoice>
One user on the german forum reported 90MB stable RAM usage during 7 days with 
2.5-16m which included patch 2806, so please try a patched version or the most 
current version which ATM is 2-5-20.

-------------------------------------------------------
Date: Wed 03/24/2004 at 12:15       By: spiralvoice <spiralvoice>
Please try this patch:
http://savannah.nongnu.org/patch/?func=detailitem&item_id=2806
One user reported on MLDonkey world that the core uses less memory with this 
patch.

-------------------------------------------------------
Date: Fri 03/19/2004 at 03:27       By: 0 <None>
i also have 512mb memory but mldonkey uses only 4%.

though mlnet does seem to have a slight leak it doesnt pass 10% for me even 
after long runs ( a month ).

check that setting relating to memory are propely set.
compaction_overhead shoudld be set low ( i use 5 default is 25 ), 
use_file_history and save_file_history should be off, for example.

if you use mlgui on the same machine you might notice that it eats more memory 
then mlnet.












For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=8187>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/







reply via email to

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