[Mldonkey-bugs] [Bug #1852] Exception sendto failed: Connection refused in sendto next / Memory leak

[nobody]

=================== BUG #1852: FULL BUG SNAPSHOT ===================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=1852&group_id=1409

Submitted by: None                      Project: mldonkey, a free e-Donkey 
client
Submitted on: 2002-Dec-02 05:23
Category:  None                         Severity:  5 - Major                    
Bug Group:  None                        Resolution:  None                       
Assigned to:  None                      Status:  Open                           
Release:  None                          Release:                                
Platform Version:  None                 Binaries Origin:  None                  

Summary:  Exception sendto failed: Connection refused in sendto next / Memory 
leak

Original Submission:  I'm seeing more and more of this messages from mldonkey

Exception sendto failed: Connection refused in sendto next

Is this because other emule peers refuse to accept incoming
connections from mldonkey?

My mldonkey also eats up all the available memory very fast. I attached a graph 
that shows the memory usage of mldonkey in a timeframe of about 5 hours. The 
maximum memory mldonkey can get on my system is bound to 32M using ulimit. I 
don't know what causes the peaks in the graph, but it would sure be nice to 
know.

I used "ps -p $MLDPID -o vsize" every 10 seconds to sample the memory 
consumption of mldonkey.

Release: 2.00
From: http://savannah.nongnu.org/download/mldonkey/stable/
Platform: Linux 2.2.20 i586 64MB RAM 128 MB Swap



No Followups Have Been Posted


CC list is empty


File Attachments
****************

-------------------------------------------------------
Date: 2002-Dec-02 05:23  Name: mem.png  Size: 5KB   By: None
Memory consumption of mldonkey over time
http://savannah.nongnu.org/bugs/download.php?group_id=1409&bug_id=1852&bug_file_id=172


For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=1852&group_id=1409