[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Mldonkey-bugs] [bugs #11149] Core does not close file descriptors and e
From: |
anonymous |
Subject: |
[Mldonkey-bugs] [bugs #11149] Core does not close file descriptors and eventually hits ulimit |
Date: |
Sun, 05 Dec 2004 17:27:20 -0500 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Galeon/1.3.17 (Debian package 1.3.17-2) |
This mail is an automated notification from the bugs tracker
of the project: mldonkey, a multi-networks file-sharing client.
/**************************************************************************/
[bugs #11149] Latest Modifications:
Changes by: Anonymous user
Date:
dim 05.12.2004 at 17:21
------------------ Additional Follow-up Comments ----------------------------
It's been a very long time since I've seen such problem on my own core. So It's
either MacOS X related, or related to the way to use mlnet.
/**************************************************************************/
[bugs #11149] Full Item Snapshot:
URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=11149>
Project: mldonkey, a multi-networks file-sharing client
Submitted by: 0
On: sam 27.11.2004 at 12:12
Category: Core
Severity: 5 - Average
Item Group: Program malfunction
Resolution: None
Privacy: Public
Assigned to: None
Status: Open
Release: 2-5-22
Release: 10.3.6
Platform Version: Mac OS X Jaguar
Binaries Origin: Downloaded from third-party page
CPU type: PowerPC
Summary: Core does not close file descriptors and eventually hits ulimit
Original Submission: It would appear that core does not always close dormant
file descriptors which causes open file descriptors to increase to the point
that core stops working due to reaching max ulimit. This happens on both
Jaguar and Panther and versions 2-5-22 and 2-5-16 of mlnet (current version of
Panther is 10.3.6). Using lsof, the problematic file descriptors look like:
mlnet 1551 jume 113u IPv4 0t0 TCP no PCB,
CANTSENDMORE, CANTRCVMORE
Hypothesize that this is due to a connection that is not closed properly at the
other end and core does not detect that the file descriptor is no longer usable
or needed. After some period of time these file descriptors keep increasing
until the ulimit is reached and core hangs.
Follow-up Comments
------------------
-------------------------------------------------------
Date: dim 05.12.2004 at 17:21 By: 0 <None>
It's been a very long time since I've seen such problem on my own core. So It's
either MacOS X related, or related to the way to use mlnet.
-------------------------------------------------------
Date: sam 27.11.2004 at 14:52 By: 0 <None>
Have discovered that the file descriptors in question are not in the file
descriptor list so that "poll" or "select" never sees them. They must have
been opened at some point but because of an error were never added to the file
descriptor list but also not closed. That is apparently why they are left
orphaned.
For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=11149>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [Mldonkey-bugs] [bugs #11149] Core does not close file descriptors and eventually hits ulimit,
anonymous <=