[Mldonkey-bugs] [bugs #1434] Locking too much memory on FreeBSD?

[spiralvoice]

This mail is an automated notification from the bugs tracker
 of the project: mldonkey, a free e-Donkey client.

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

Changes by: 
                spiralvoice <address@hidden>
'Date: 
                Tue 12/02/2003 at 19:15 (Europe/Berlin)

            What     | Removed                   | Added
---------------------------------------------------------------------------
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
This patch report is very old. If the bug still exists in current

versions please post a new bug report - spiralvoice






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

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=1434>
Project: mldonkey, a free e-Donkey client
Submitted by: Claas Rathje
On: Thu 10/17/2002 at 15:47

Category:  Core
Severity:  5 - Average
Item Group:  memory leak
Resolution:  None
Assigned to:  None
Status:  Closed
Release:  None
Release:  2.00
Platform Version:  FreeBSD i386-i686
Binaries Origin:  Compiled From CVS


Summary:  Locking too much memory on FreeBSD? 

Original Submission:  Hi there,

I updated my CVS version today morning, fired it up and went to bed. As I woke 
up and looked on my terminal I saw that mldonkey currently locks up 260MB RAM 
with only 4 files in the list and none currently shared. Well, it's a CVS 
release, maybe tonight was something wrong, so I updated again 40min ago and 
now I see that it is eating up my RAM again, 55MB after 40min is not what I 
think is normal, or am I wrong? 

I had same problems some time ago (see atached file) with the CVS releases from 
1.99, it were even worse, it ate so much RAM over just one night that my 
FreeBSD-Box (450Mhz, 256MB RAM, 256MB Swap) was totally down, nothing worked, 
not eaven the real consoles as I crawled in my attic and connected a display. 
So I think it is not really fixed by now, is it?



Besides of the mem-leaks that I have (don't know weather I'm alone with this 
problem) I think you did/are doing a really good job with mldonkey because it 
is the fastest client that I ever tested and it does not need windows ;) Great.



So long...

Ca$cAdE

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


-------------------------------------------------------
Date: Tue 12/02/2003 at 19:15       By: spiralvoice
This patch report is very old. If the bug still exists in current

versions please post a new bug report - spiralvoice

-------------------------------------------------------
Date: Sun 09/28/2003 at 14:48       By: None
I had the same problem. Yesterday I updated to the release-2-5-devel branch 
(CVS version) and now mlnet only needs ~64MB of RAM (it typically needed over 
300 MB before).

-------------------------------------------------------
Date: Mon 08/11/2003 at 10:11       By: None
Problem is also present on Linux using the 2.5-3 binary release. Seems like its 
a memory leak in mlnet, and a rather severe one at that.

-------------------------------------------------------
Date: Thu 07/31/2003 at 05:44       By: None
i have the same problems and I am on 5.1 release

-------------------------------------------------------
Date: Sun 12/22/2002 at 13:51       By: None
i have the same problem, too. running freebsd 4.4



-------------------------------------------------------
Date: Fri 11/29/2002 at 12:38       By: jentaoris
same problem with slackware 8.1 and kernel 2.4.19



anythign new with this?!?!?!?!?

-------------------------------------------------------
Date: Thu 11/07/2002 at 06:32       By: None
Same problem with Mac OS X 10.2.1 and the stable 2.00...

-------------------------------------------------------
Date: Tue 10/22/2002 at 19:56       By: None
Hi I'm the Debian guy.

If I limit the max_hard_upload_rate I have no problems anymore.

btw. thank you all for coding mldonkey!



-------------------------------------------------------
Date: Tue 10/22/2002 at 00:40       By: None
And i have this problem with RedHat7.0/Linux too. (CVS Version)

-------------------------------------------------------
Date: Mon 10/21/2002 at 20:55       By: None
I have the same problem with Debian GNU/Linux and the stable 2.00!

-------------------------------------------------------
Date: Mon 10/21/2002 at 20:51       By: None
I have the same problem with Debian GNU/Linux and the stable 2.00!

-------------------------------------------------------
Date: Thu 10/17/2002 at 15:53       By: cascade
Okay, the upload thing did not work:

Warning: File Upload Error - No Mime boundary found after start of file header 
in /subversions/sourceforge/src/savannah/www/bugs/index.php on line 0



So I decided to upload the picture somewhere else so that you all can see what 
I mean with locking up too much memory ;)

And here it is: http://deloew.de/cascade/temp/swap.png 



btw: My FreeBSD version is: 4.3-RELEASE-p20

and mldonkey currently uses:

53546 work           56   0 75108K 73624K RUN     46:25 41.21% 41.21% mldonkey



I hope this gets fixed because it's not that much fun always looking on the mem 
that mldonkey uses to prevent your box from crashing.



So long...

Ca$cAdE












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

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