mldonkey, a multi-networks file-sharing client - Bugs: bug #7222, Memory leak in mldonkey still...
You are not allowed to post comments on this tracker with your current authentication level.
bug #7222: Memory leak in mldonkey still exists and is quite bad.
Submitter: | Joseph R. Kiniry <kiniry> | ||
Submitted: | Tue 13 Jan 2004 01:10:01 PM UTC | ||
Category: | Core | Severity: | 3 - Normal |
Item Group: | Memory leak | Status: | Fixed |
Assigned to: | None | Open/Closed: | Closed |
Release: | 2-5-21 | Release: | |
Operating System: | Linux | Binaries Origin: | CVS / Self compiled |
CPU type: | None |
Jump to the original submission
Tue 24 Aug 2004 10:01:40 AM UTC, comment #17: |
Joseph R. Kiniry <kiniry> |
Sun 22 Aug 2004 12:14:32 PM UTC, comment #16: I was out of town on-and-off for a few weeks. Sorry for the delay. I have built the latest CVS snapshot that you indicated and it is running now. I will have data for you in the next day or two. |
Joseph R. Kiniry <kiniry> |
Sat 21 Aug 2004 11:37:11 AM UTC, comment #15: You can find a tarball of current CVS here:
|
spiralvoice <spiralvoice> |
Tue 10 Aug 2004 08:42:40 PM UTC, comment #14: May I simply build the CVS HEAD (or HEAD at a specific date) rather than download a tarball to build?
|
Joseph R. Kiniry <kiniry> |
Tue 10 Aug 2004 06:42:57 PM UTC, comment #13: Please check if this bug still is in current CVS version.
|
spiralvoice <spiralvoice> |
Sun 23 May 2004 09:00:55 PM UTC, comment #12: Have you tried the memory leak fix patch on savannah? It fixed the problem for me. |
Anonymous |
Thu 13 May 2004 09:41:27 AM UTC, comment #11: As mentioned in the last response, I am now running 2.5.21. It has been running now for 11 1/2 hours.
|
Joseph R. Kiniry <kiniry> |
Tue 11 May 2004 09:53:01 AM UTC, comment #10: I updated to release-2-5-21 and am now testing it. Oddly, when I press the "Help+" button in the HTTP-based interface it reports: "MLNet 2.5-18". After running for about 10m mlnet is using 26.5MiB of memory. I'll let it run for a few days and report back the change in memory use at that time. |
Joseph R. Kiniry <kiniry> |
Sat 08 May 2004 08:33:37 AM UTC, comment #9: Dear Mr Spiralvoice,
|
Anonymous |
Tue 04 May 2004 07:21:43 PM UTC, comment #8: Please check if this bug still is in current CVS version.
|
spiralvoice <spiralvoice> |
Sun 25 Apr 2004 06:22:45 PM UTC, comment #7: Dear Mr Spiralvoice,
|
Anonymous |
Sat 03 Apr 2004 06:43:10 AM UTC, comment #6: well, i had severe issues with this, but i downloaded Spiral's 2.5.16f and it's been running for 60 something hours straight.
|
Anonymous |
Fri 26 Mar 2004 10:51:17 AM UTC, comment #5: There are some patches on Savannah which address upload slots problems but users reported that these also sloved their memory problems. |
spiralvoice <spiralvoice> |
Wed 18 Feb 2004 01:29:23 AM UTC, comment #4: My situation: P100, 48 Mb RAM, using 2.5-12. Self-compiled on RH8, enabled Overnet and SoulSeek. With 4 files to download (and 30 shared) MLdonkey starts with 9 Mb of memory and grows to about 15 Mb in 10 mins. This is reasonable: servers are connected, peer lists populated, downloads started and all functionality works. But after first 10 mins, memory is consumed at a constant rate of approx. 2 Mb/h, without any changes in speed/peers/servers/files. |
Anonymous |
Thu 15 Jan 2004 03:41:31 PM UTC, comment #3: The aforementioned log is only 3.4MB (!) when bzipped, so if an mlnet developer wants a copy, just drop me an email. |
Joseph R. Kiniry <kiniry> |
Thu 15 Jan 2004 03:26:43 PM UTC, comment #2: mlnet has now been running for ~28 hours. Exactly two files are being downloaded (at ~2Kb/s), and five files are being uploaded (at ~21Kb/s). mlnet is now using over 100Mb of resident memory:
|
Joseph R. Kiniry <kiniry> |
Tue 13 Jan 2004 01:14:01 PM UTC, comment #1: |
Joseph R. Kiniry <kiniry> |
Tue 13 Jan 2004 01:10:01 PM UTC, original submission:
I'm a bit surprised this has gone on as long as it has. I see bug reports on bad leaks that go back almost 16 months.
|
Joseph R. Kiniry <kiniry> |
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 13 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2004-08-24 | spiralvoice | Open/Closed | Open | Closed | |
2004-08-24 | spiralvoice | Status | None | Fixed | |
2004-08-21 | spiralvoice | Release | release-2-5-4 | ||
2004-08-21 | spiralvoice | Release | 2.00 | 2-5-21 | |
2004-03-16 | spiralvoice | Dependencies | - | Depends on bugs #3761 | |
2004-02-11 | t8m | Carbon-Copy | - | Added t8m | |
2004-01-15 | kiniry | Attached File | - | Added Sources.txt, #965 | |
2004-01-15 | kiniry | Attached File | - | Added Overnet.txt, #964 | |
2004-01-15 | kiniry | Attached File | - | Added Memory.txt, #963 | |
2004-01-15 | kiniry | Attached File | - | Added Gnutella.txt, #962 | |
2004-01-15 | kiniry | Attached File | - | Added eDonkeyTable.txt, #961 | |
2004-01-15 | kiniry | Attached File | - | Added eDonkeyList.txt, #960 | |
2004-01-15 | kiniry | Attached File | - | Added ConnectedServers.txt, #959 |
Powered by Savane 3.13-d3ae.
Corresponding source code
After running a build of the latest CVS snapshot for several days, transferring a dozen or so large file (i.e., my typical usage), the mlnet client seems to use a reasonable, linear amount of memory. Thus, based upon my testsing, mlnet no longer seems to have the serious memory leak I reported.
Initial memory use was between 10 and 20MB, and maximal memory use is around 50MB:
1928 kiniry 10 0 47136 45m 2624 S 0.3 4.5 22:40.86 mlnet