Tue 02 Mar 2004 12:37:31 AM UTC, original submission:
Moin,
I'm seeing something not completely unlike bugs #7222 in that my self-compiled 2-5-12 eats a lot of memory.
However, the mldonkey-2.5-4.static.i686-Linux.tar.bz2 I used before didn't.
So I think the problem lies maybe not in the mldonkey itself but in the way we compile it, ie gcc & libs ...
What happened here is:
After running since Jan 2, on Feb 25 I shut down the old mlnet 2.5-4:
637 mow 14 0 39704 38M 2088 R 0 2.1 31.1 2278m mlnet
As you can see, memory usage is quite low. Download was about 3.4GB during that time, with about 12GB upload.
Then I installed the newly-built 2-5-12 (by the way, thankyouverymuch for rm-rf'ing the ocaml tree after copying the libs to the safe place failed due to insufficient disk space, thus having to compile the stuff a second time).
The new mldonkey quickly went to download and even appeared to perform better than the older version, and initially even the memory footprint looked better:
8602 mow 12 0 15156 14M 2824 R 0 25.5 11.8 2:01 mlnet
However, it didn't stay like that.
Due to a power outage, I had to boot up the machine on Saturday.
This morning, I found mlnet was dead.
A straight line in mldonkeywatch stats.
Memory footprint now didn't look so good:
892 mow 7 0 170M 106M 2472 D 1 3.5 85.9 228:33 mlnet
strace -p 892 showed ... nothing.
lsof showed 125 open thingies.
telnet to 4000 also hung.
I then murdered mlnet by sending an -IOT/ABRT.
Then tried to restart:
[...]
File ./fasttrack.ini.tmp exists
An error may have occurred during previous configuration save.
Please, check your configurations files, and rename/remove this file
before restarting
SAVING SHARED FILES AND SOURCES
SAVED
Network.save_complex_options not implemented by BitTorrent
Options correctly saved
What mlnet did, is:
a) remove said fasttrack.ini.tmp itself
b) move servers.ini, files.ini, file_sources.ini, friends.ini, shared_files_new.ini to .old and put default files in their location.
Maybe rotating .ini files and then bailing out before writing new ones is not that good an idea.
Okay, next start:
"Looks like you have no servers in your servers.ini"
... yes, thank you, you just removed them. Okay, apparently you got yourself a new list, too, so I won't complain much.
Well, mlnet starts up, all seems fine ...
... except, a bunch of file names from the downloads are missing, only the hashes show. [btw, mldonkeywatch nitpick, don't know if the problem lies with mldw or with mlnet itself: changing to another filename from the dropdown list reverts to the old filename on the next refresh]
Now, hashes got replaced by filenames as files were found.
However, "pause" settings were gone also.
Now mlnet has been running for 10h16mins.
mow 23887 9.5 65.9 87124 84016 ? S 13:25 58:58 mlnet -daemon
That's quite a lot of memory.
Now, let's see what we have here:
# ldd /usr/local/bin/mlnet
libz.so.1 => /usr/lib/libz.so.1 (0x4001d000)
libm.so.6 => /lib/libm.so.6 (0x4002c000)
libdl.so.2 => /lib/libdl.so.2 (0x4004e000)
libc.so.6 => /lib/libc.so.6 (0x40052000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
those libs pointing to:
-rwxr-xr-x 1 root root 55772 Mar 11 2002 /usr/lib/libz.so.1.1.4*
-rwxr-xr-x 1 root root 561250 May 26 2001 /lib/libm-2.2.3.so*
-rwxr-xr-x 1 root root 72701 May 26 2001 /lib/libdl-2.2.3.so*
-rwxr-xr-x 1 root root 4787276 Jan 11 2002 /lib/libc-2.2.3.so*
-rwxr-xr-x 1 root root 432647 May 26 2001 /lib/ld-2.2.3.so*
Compiler:
# gcc --version
2.95.3
Machine:
Linux good 2.2.26ext3 #4 SMP Thu Feb 25 05:30:18 CET 2004 i686 unknown
configure invocation:
$ ./configure
(auto-gets and builds ocaml-3.07pl2)
... followed by make depend and make, as told.
Now, it would be really interesting whether a mldonkey-2-5-12-static built in the same way as the 2.5-4-static leaks or not. Could the one who produced those binaries please do so again, that I can test whether it's mldonkey or just my environment that acts up?
BTW: This is a machine with two DSL lines. Default route is on the PPPOE interface, thus changing IP every 24 hours.
The old 2.5-4 first ran on the PPPOE line, then kept getting more and more (Overnet?) connects over the fixed IP line, leading to, at first, IP-flapping in the mldonkeywatch Settings:Core window, then after a few weeks it stood solid on the fixed IP. A problem was, that some servers then complained "ERROR: Your userhash doesn't match the login one", so it seems mldonkey sent something based on the wrong IP. Unfortunately, I can't check that with 2-5-12 because it simply doesn't run long enough.
Hope that made sense.
MOW
(mlnet has now 100840K. Shutting down in a few.)
|